Blog #7: Debugging Maxim’s Firmware Framework Crash

RE: Blog #7: Debugging Maxim’s Firmware Framework Crash

dougw — Tue, 08 Nov 2022 17:45:51 GMT

Wow, Great documentation of in depth troubleshooting techniques. Finding the problem with someone else's sloppy code can be a very tough task. Thanks for posting.

RE: Blog #7: Debugging Maxim’s Firmware Framework Crash

shabaz — Tue, 08 Nov 2022 02:31:04 GMT

Good detective work : )

There may have been a compiler warning, but with the large body of code (especially all the Mbed libraries) it would be very easy to miss that, and as you say, it's not something that you'd expect to cause that type of issue at first glance.

CLion incidentally will pick up this sort of error as you type, which is really nice. Probably VS Code and others will do too.

Still, if the IDE had picked it up earlier, then you wouldn't have got the opportunity to share this nice investigation : )

GDB is extremely powerful, especially with a bit of assembler knowledge. It got me out of a lot of trouble on commercial software (written in C/C++ for Solaris and Linux) with literally just a days worth of scanning through the Intel and UltraSPARC instruction sets as I went along (i.e. it's not essential to be an assembler expert, in case it initially looks scary to people).

RE: Blog #7: Debugging Maxim’s Firmware Framework Crash

rsjawale24 — Mon, 07 Nov 2022 19:03:35 GMT

Very well documented and great debugging skills. I tried debugging with openocd and MAX Pico board but I'm a beginner and still learning it.

It took me more than 2 hours to read the blog and understand certain things.