Exception Crash reporting - dalathegreat/Battery-Emulator GitHub Wiki

What is a crash?

:warning: Warning: The board was reset due to an exception or panic. Inform developers!

If you are seeing this message, it means the embedded code on the board crashed fatally, which resulted in an automatic reboot. This is unwanted behavior, and should be investigated by a developer.

How do I help?

By providing debug logs and reporting a Github issue! This is explained in the steps below:

Step 1: Gather logs

If you are seeing panic resets, connect the USB cable to a PC, and enable serial monitor in the Arduino IDE. Let the log capture all data that the board spits out, and when the Panic reset occurs, store all the text into a .txt file.

:information_source: Remember to set baud rate to 115200 in the right hand side of the monitor, otherwise all text will be garbage =!"=%(=?!

This is what a reboot might look like

assert failed: xQueueGenericSend queue.c:872 (pxQueue) Backtrace: 0x40082ce1:0x3ffd12a0 0x4008c611:0x3ffd12c0 0x40091cda:0x3ffd12e0 0x4008c9ff:0x3ffd1410 0x400ed07f:0x3ffd1450 0x400da90e:0x3ffd1490 0x400da847:0x3ffd14e0 0x400d6d58:0x3ffd1500 0x400d6da2:0x3ffd1520 0x400d3779:0x3ffd1540 ELF file SHA256: 575c5caf3b3eb57e Rebooting...

Step 2: Store what configuration you are running.

By saving the USER_SETTINGS.h and USER_SETTINGS.cpp , you will also help the developers figure out what software combination is active.

:information_source: Be sure to remove any potential Wifi / MQTT credentials from the files before saving them!

Step 3: Make a Github issue

The final step, is to make a descriptive issue on Github. A new issue can be created via this link: Make new issue

Remember to post the Debug file, USER settings files, and an overall description on how frequent the panics occur, and if there is any easy way to reproduce it.

Thank you for helping improve the software!