3 ms·
This is a helpful tutorial for beginners. What would be really be helpful to me is a compendium of what has been found not to work. Every microcontroller has a
by ncmncm 6y ago
This is a helpful tutorial for beginners.
What would be really be helpful to me is a compendium of what has been found not to work. Every microcontroller has a horrendous, secret list of stuff that is just broken, and the only way usually to find out is to try to use it and fail. If you get somebody from the vendor to talk to you, they say they knew all about it already.
For example, ESP32 is supposed to be actually useless for low-power applications, because its sleep modes are messed up, somehow; maybe it doesn't wake up reliably, or does when it shouldn't? Also it draws more power than it should in a sleep mode.
Lots of the on-chip peripheral gadgets have very non-obvious failure modes. I guess you are supposed to expect trouble synchronizing things with different clocks: "Check this flag bit twice before you trust it." Special added non-standard instructions have gotchas like "turn off interrupts while this instruction runs", or "don't let these instructions write to memory; get the results in registers and copy them out".
It seems like a wiki would be a good way to compile lists like this, but engineers who program microcontrollers mostly don't seem to think that way. Too, many have signed NDAs or don't want the vendor mad at them.
- elcritch 6y agoTotally! Just worked around a few ESP32 issues, though at least their GH repo is full of discussions on various broken parts. Just had a SAMD processor routinely fail on me in a non-obvious way. It's annoying how segmented and walled off the embedded hardware types are as a field. Lots of hardware parts come their own idiosyncrasies. I wish Digikey/Mouser had a ratings/review system for parts.