Home > On-Demand Archives > Talks >
Adventures in Debugging
Alvaro Prieto - Watch Now - Duration: 42:19
Have you ever had tricky, hard-to-find bugs in your hardware/firmware? Me too!
Join me while we go through some past troubleshooting and debugging adventures and learn various techniques and tools in the process!
Some topics might include:
- GDB and python
- Various signal probing techniques
- Simple tracing (without additional hardware!)
- Debugging remote devices
- Useful (and not-so-useful logs!)
- Fatfs performance lessons
Hi Alvaro,
Very informative presentation, thanks for sharing the details for the ventures with us. The Python bindings for GDB look really cool, I will be checking those out right after this comment :).
Although not directly related to debugging, I am curious about a couple of points.
- What's the main decision behind using dynamic allocation for your application?
- Ignoring the monetary constraints of Iridium comms, do you think it would be technically possible to send a binary image to effectively support OTA or are there inherent limitations imposed by the short burst nature of this bearer?
Thanks
Thanks Raul!
Honestly, the main reason I went with dynamic allocation was development speed and flexibility. We could have done most of what we're aiming for with static allocation or pre-allocated fixed buffers, but that would have taken much more time up front, which we didn't have, unfortunately.
Also, due to the device's configurability, it's nice not having to re-compile when I want to give more resources to a certain task (RAM buffering SD logs was a huge performance win, but I allocate different sized buffers depending on how often we write to the logs). There's also some very high speed operations (I2S microphone sampling) which benefit from huge buffers but only for short bursts of time.
On the Iridium side: Nothing technically stops us from receiving an update image over several days. Monetary constraints aren't the only ones with Iridium SBD though. We are unable to receive a message without first transmitting one, so the power costs are enormous too!
I use CubeMX but also find it clunky with USB in particular, as it doesn't support composite classes. Why would you use GDB over a visual debugger in your IDE? Have you used SystemView or Tracealyzer?
Thankyou, that was very informative and well presented!
Such a cool presentation! Thanks a lot for sharing, almost 100% of similar situations happened in my career too..
Great presentation. The lessons learned with the SD logging are interesting, especially since a couple of them have parallels elsewhere in software.
Debugging is fun and enlightening. Discerning HW vs SW issues is why you do need to have the ability to get into both sides of it to understand the issues that "might" be. Very good show and tell of what you ran into and how to chase them with the many tools that it takes.
Great debugging stories,. thanks
Great presentation, Alvaro! It was very helpful to see you walk through the thought process on how to track down complex issues. Also, I have those same magnetic probes and I tell everyone I can about them - they are fantastic!
Thanks for your presentation, Alvaro. Watching a bit later than everyone else! It's always so interesting to learn about strange behavior and how to debug them, especially in embedded systems, where it's not always clear whether the issue is software, hardware, interfaces, or something else. It's rare to get a glimpse of someone else's experiences and thought processes to learn from them. Thanks for putting it out there!