I’m intrigued by the potential for rust in the embedded space. As
a platform for experimentation, I purchased an STM32 F4 discovery
board. I chose the F4 model to match the CPU on typical racing
drone flight controllers without realising the higher level of
support for the corresponding F3 discovery board.
I was initially running svd2rust for the STM32F407 device, but I’ve
subsequently found the STM32F4 support in the generic stm32-rs crate
and I’ve got to the stage where I’ve got trivial demos working. I’m
now starting to look at the HAL layer, amd I’m unsure which way to
go. I noticed that the stm32f429-hal crate exists, but it’s a fork of
the stm32f30x-hal crate, and it’s not clear to what extent the forked
features work or have been tested.
I’m tempted to create a new hal crate of my own, which will start
empty and into which I will incrementally port and test features from
Thoughts? Is this a reasonably approach? I’m impressed with the
svd2rust tooling to automate low level API generation, but it seems
there’s still a lot of work required to get embedded_hal support for
an unsupported device.