-
Notifications
You must be signed in to change notification settings - Fork 2
Description
I'm working on a open-source project that targets an stm32f205(rgt6, fwiw) in an application where memory safety is paramount. I'd really love to go full-Rust instead of some hybrid C-bootstrap-plus-Rust type of thing, and you guys have helpfully provided a PAC for the f2 family. Unfortunately, though, there's no proper HAL.
So far I've been giving it a good old college try on a fork of stm32f1xx-hal, using AN3427 as guidance to update it for the F2 series. I think I got the RCC changes done, but I'm finally realizing that the F1's AFIO is gone in F2 and maybe I should have started with F4 instead even though there's no handy application note for that.
Anyhow, it seems like I should probably ask the experts at this point. How hard actually is cooking up a HAL for the F2? Is doing so something anyone else has an interest in? Would a potential collaboration be in order?
My budget's not unlimited -- especially given that I still have to convince the rest of my team that Rust is the way to go here -- but it's possible that I'd be able to swing an arrangement to sponsor someone to do the port. Is that something anyone might be interested in?
(For context, my particular project needs the RCC (there's an external 8MHz crystal, and the CSS would be nice), the OTG_FS peripheral in device mode, and GPIO for some inputs, a couple of LEDs, and some bit-banging I have to do to drive an OLED screen. That's about it, though -- No USART/SPI/I2C/I2S or Ethernet or CRC/crypto/hash accel or anything fancy.)