stm32f3xx-hal
stm32f3xx-hal copied to clipboard
stm32-rs
A Rust embedded-hal HAL for all MCUs in the STM32 F3 family
Lately this project seems to be quite undermaintained. There are a couple of PRs open currently that would be useful to have merged, but they don't get reviewed. I think...
Either, monitor the binary sizes of the examples or write a binary, which does use almost every function to monitor each module. Use https://github.com/orf/cargo-bloat-action/ for that.
Having one stop enum for all toggle-able things doesn't feel like a right abstraction. (Yes, this issue should be opened before 0.8.0 release 😢)
I struggle to use this crate to execute basic I2C requests with timeouts. Can you provide an example on how to use the I2C abstraction with timeouts to ie scan...
Constructors for peripherals with more sophisticated configuration method should be able to fail. Something like [stm32f4xx-hal](https://github.com/stm32-rs/stm32f4xx-hal/blob/9321be1dea08befe18b547fc4edc946e2c6db057/src/serial.rs#L657-L663) did.
So that this is not needed: ```rust use stm32f3xx_hal as hal; use hal::spi:Spi; use hal::pac::SPI1; //
We should likely update [`awesome-embedded-rust`][] and also [`stm32f30x-hal`][] to point to this crate since this crate is actively maintained. Related issue: https://github.com/japaric/stm32f30x-hal/issues/36 - [X] Switch [`awesome-embedded-rust`][] from pointing to [`stm32f30x-hal`][]...
# Summary The current way we go about this is both un-ergonomic and unsound. ## Current Usage Today, the strategy for handling registers like these is to allow only the...
Rename [`downgrade`](https://github.com/stm32-rs/stm32f3xx-hal/blob/fc5c0a6a7010650d5a367a2cb4faf657053bc93d/src/gpio.rs#L399) to `erase_pin` or similar to conform to [C-ERASED-PIN](https://rust-embedded.github.io/book/design-patterns/hal/gpio.html#pin-types-provide-methods-to-erase-pin-and-port-c-erased-pin)