4 ms·
The main official tools I use: - Stm32CubeIDE: Graphical IDE, sort of, that shows you how to configure the peripherals. I mainly use it to get clock scalers
by the__alchemist 1y ago
The main official tools I use:
- Stm32CubeIDE: Graphical IDE, sort of, that shows you how to configure the peripherals. I mainly use it to get clock scalers and linker config, but you can use it to configure all peripherals. Note that the linker config is straightforward for most STM32s, but is messier on H5 and H7.
- Stm32CubeProgrammer: Flashing for production use, e.g. in DFU mode
I've been using Rust tools for everything else. I had to built a lot of tooling along the way (HAL and interaction with specific peripherals), but it was worth it. There's some boilerplate, but it's not too bad.
The PAC team has done a great job smoothing over errors in ST's IDE. The Knurling team behind `defmt`, and the probe-rs team have also be integral to this being a smooth experience. I'd go as far as saying this is one of rust's core strengths. (Easy builds and in embedded constext, flashing/debugging)
The workflow to build and flash with debugging is: `cargo run --release`.