3 ms·
The boot process you describe is a side effect of using external flash. Microcontrollers with internal flash like the STM32 will just start executing at a certa
by Goz3rr 5y ago
The boot process you describe is a side effect of using external flash. Microcontrollers with internal flash like the STM32 will just start executing at a certain memory address depending on which boot mode is selected.
I'm curious what you think made the STM32 worse however, as in my experience they have good documentation and good options for the development software (and also a few not so good ones)
- mmoskal 5y agoI particularly "like" the how they copy&paste manual sections for TIM1, TIM3/4, TIM6/7, TIM14, TIM15/16/17 (this is from STM32G0). I get it, there are some features only available on say TIM1, but why on earth would just copy everything, instead of having one TIMx section and saying "only available on TIM1-4" on specific registers? It's particularly fun if you want to write a driver for all TIMx - you have to de-dup in your head. I find the LL (low level) library from STM relatively nice; OTOH their (high-level) HAL is plain awful. Simply writing registers isn't too bad either, especially that even in that case what you write will mostly work across their different microcontrollers. In general, I find the NRF52 docs and hardware to be much more straightforward but it could be that they don't have to support every single feature on the planet like STM ;) edit: typos, wording