A dump of an earlier firmware crash was saved
What ArduPilot says:
- Saved crash_dump.bin
- Logging …
When the firmware itself crashes (a hard fault in the code, not the aircraft hitting the ground), ArduPilot keeps a snapshot of memory in the board's flash. On a later start the logging thread copies it to the card as APM/crash_dump.bin, trying every 5 seconds until a card is there (“Saved crash_dump.bin”), and writes it into the log too (“Logging @SYS/crash_dump.bin”). The same finding blocks arming as “CrashDump data detected”.
What to do, most likely first
The firmware crashed on an earlier run: a bug, most often in a test build, a custom build or a script binding.
CheckWhat changed before it appeared: new firmware, a new script, a new device? Was the aircraft flying at the time? Look for a “WDG:” line and internal errors after the same start.
FixDo not fly until you know why. Keep crash_dump.bin and the log, go back to the stable release for your board, and report the crash to the ArduPilot developers with both files and the exact firmware version.
Where to do it:Setup & Tuning GuideSetup & Tuning Guide
The code that sends it
Saved crash_dump.bin
libraries/AP_Logger/AP_Logger.cpp AP_Logger::check_crash_dump_save() · Open in ArduPilot Copter-4.7.1
Logging …
libraries/AP_Logger/AP_Logger.cpp AP_Logger::file_content_update() · Open in ArduPilot Copter-4.7.1