stm32f4xx-hal
stm32f4xx-hal copied to clipboard
stm32-rs
A Rust embedded-hal HAL for all MCUs in the STM32 F4 family
ST Refernce Manual RM0090 suggests using `PSIZE_X64` when external Vpp is applied, `PSIZE_X32` when voltage is between 2.7V and 3.6V, `PSIZE_X16` when voltage is between 2.1V and 2.7V and `PSIZE_X8`...
Currently the `serial` function requires a tuple of RX/TX pins. The [reference manual](https://www.st.com/resource/en/reference_manual/rm0390-stm32f446xx-advanced-armbased-32bit-mcus-stmicroelectronics.pdf) states that "the TX and RX lines are internally connected", so only one pin would be required...
In `SpiBus::transfer` ```rust fn transfer(&mut self, read: &mut [Word], write: &[Word]) -> Result; ``` From [embedded-hal docs](https://docs.rs/embedded-hal/1.0.0-alpha.9/embedded_hal/spi/trait.SpiBus.html#tymethod.transfer): >**It is allowed for read and write to have different lengths, even zero...
I'm playing around trying rust embedded for the first time using an existing board-stack with an F413 I have which has the UART4 for "debugging" but it seems the formatting...
case: examples/ssd1306-image.rs mcu: stm32f401 in proteus hal version: stm32f4xx-hal = "0.13.2" problem: through proteus's I2C debugger, find only occurs "S 78 A P", then the MCU hang. the final positon...
It seems the function `UnlockedFlash::program()` can write outside the bounds of the flash memory if given an invalid offset: https://github.com/stm32-rs/stm32f4xx-hal/blob/6d0c29233a4cd1f780b2fef3e47ef091ead6cf4a/src/flash.rs#L239-L241 One way to improve this might be to check `offset`...
