3 ms·
What I want to know about a microcontroller is, (a) can I use Make/Gcc/Gdb to develop for it without a lot of guesswork, and (b) what is its interrupt latency?
by ncmncm 6y ago
What I want to know about a microcontroller is, (a) can I use Make/Gcc/Gdb to develop for it without a lot of guesswork, and (b) what is its interrupt latency? The article only hinted at (b) for a couple of them, and said practically nothing about (a). IDEs are a trap.
- jhallenworld 6y agoI recommend STM32CubeMX: this is a GUI tool that creates a gcc/ makefile project for any of their micros- so you only have to use it once to set up an example "hello world" project. No IDE is needed (older versions only generated code for IDEs, but no longer). If you follow the comments in the generated source code you can keep your code separated from their code. The advantage is that you can reconfigure your project later- for example to change microcontrollers, or enable new peripherals.
- SV_BubbleTime 6y agoI tried but HATED my code being stuffed between comment blocks of //USER CODE GOES HERE// There were four or five of those blocks in my main alone. It’s a dumb thing but was driving me nuts. If you break your code away from there’s ASAP it’s probably better.
- spfzero 6y agoInterrupt latency is always well covered in device docs, and pretty easy to find. And, honest question, isn’t it basically determined by the architecture and clock speed? So for instance, an ARM Cortex 0+ at 40 MHz, same in every family?
- ncmncm 6y agoIt is determined by the architecture, clock speed, memory architecture, time to wake from sleep, etc. So, some ISA, some other stuff. If you are familiar with the arch, you can guess pretty well, but in a big survey it seems like the point is you aren't.