Inkplate debugging: attaching debugger and reading crash dumps

Customer:

I’m new to embedded programming and stuck with debugging Inkplate. I don’t see anything in the Inkplate docs about how to attach the Arduino debugger, and the default setup doesn’t work—it says it’s missing a debug.cfg file. I also have no idea how to read the dumps caused when my program crashes. Is there some way to correlate the register dump/backtrace to my original source code? Did I completely miss some crucial documentation about debugging?

Originally submitted via email support on 4 March 2025. Migrated to the forum for community visibility.

Soldered Support:

Inkplate is based on ESP32, so its debugging capabilities are those of the ESP32. For debugging, we recommend using the ESP32 exception decoder: GitHub - me-no-dev/EspExceptionDecoder: Exception Stack Trace Decoder for ESP8266 and ESP32 · GitHub. There is a detailed tutorial in the README. This is how you read the dumps which get printed over Serial at 115200 baud. If you’re having problems with refreshing the display on Inkplate, try uploading the basic black and white example. If you’re using the Soldered Inkplate 6 board definition, use the e-Radionica Inkplate 6 board definition instead, and vice versa. This usually helps remove the issues with the display not refreshing.