Hi All!
I am experimenting with some aerodynamically unstable designs. The drone lost stability in flight and started tumbling (this was expected), got back under control, and landed softly.
On the next turn-on, I received the crash dump message.
crash_dump.bin (113.4 KB)
Below is the link to the log:https://drive.google.com/file/d/1geA35HlMNXQDclukhihT76XnYudxM-Bc/view?usp=drive_link
Thank you!)
Log has an access requirement. Please remove that. Thanks.
Changed the access settings, thank you for picking this up!
I checked the flight log and the crash dump.
The tumbling itself does not appear to have directly caused the flight controller to reboot. The log shows an EKF3 lane switch and vibration compensation during the unstable flight, but the vehicle continued running afterward and was normally disarmed.
However, the crash dump does indicate that a firmware/CPU fault occurred at some point.
One thing that stands out is:
PC = 0x30001FB8
LR = 0x0815DEFF
The PC appears to point into RAM rather than the normal firmware code region, while the LR is still in the flash/code region.
This could indicate something like an invalid branch/return, stack corruption, or memory corruption, although it would need to be symbolized against the exact ArduCopter 4.6.3 ELF file to determine the actual cause.
So I don’t think the crash dump was simply caused by the drone tumbling. The unstable flight definitely caused significant EKF/vibration events, but the actual crash dump looks more like a separate software/CPU fault.
It would be useful for an ArduPilot developer to decode the crash dump using the exact firmware ELF.
Got the log of the flight that preceded this one?
I thought it probably had something to do with the flight instability and forgot to add some info:
Two flights were in one log, and after the first flight, some settings (ANGLE_MAX and LOIT_SPEED) were changed using the MLRS data radio.
I am not sure if this could have caused the problem.
Thank you!
Yes, here is the link.
Thank you!
@Jack5 is on to it.
PC 0x30001FB8 → execution in RAM
LR 0x0815DEFF → return/caller address in firmware flash
Exception → HardFault
