Earlier i’ve tried to reflash the firmware, after reflashing the error disappeared for some time, but now its poping up again and again, i’ve also tried replacing memory card but it didn’t helped much.
I apologize. I thought you had already posted this issue previously. It was a different user, and I’m afraid I just encouraged you to make too many duplicate posts. No worries, we can just continue the discussion here.
I will take a closer look tomorrow if no one else responds first.
After reviewing the documentation, I identified two possible root causes:
Firmware-related issue
I. Possible firmware corruption
II. Stacking-related problem
III. Any other firmware-related fault
Hardware-related issue
I. Cube
II. Memory card
To validate these possibilities, I conducted multiple controlled bench tests (static testing, without propellers).
Test Cases & Results
Case 1 – Firmware Downgrade (Original Memory Card)
Downgraded firmware from v4.6.2 to v4.5.5
Selected v4.5.5 because I have completed 200+ successful flights on this version (on another platform), considering it a stable build.
No other changes were made to avoid introducing unknown variables
Used original Cube Orange+ memory card (Class 10, 64 GB)
Result:
The vehicle restarted after some time and error pop up.
Case 2 – Firmware Upgrade (Original Memory Card)
Fresh installation of v4.6.2
Same original Cube Orange+ memory card (Class 10, 64 GB)
No other changes
Result:
The drone booted, and the same issue persisted.
Case 3 – Memory Card Replacement (v4.6.2)
Firmware kept at v4.6.2
Replaced original memory card with SanDisk 32 GB
Multiple repeated test runs
Result:
No error observed. System operated normally.
Case 4 – Memory Card Replacement (v4.5.5)
Firmware set to v4.5.5
Used SanDisk 32 GB memory card
Multiple repeated test runs
Result:
Same as Case 3 — no error observed. System operated normally.
Additional Notes
All tests were conducted on the bench (static testing, without propellers).
Multiple repetitions were performed to confirm consistency of results.
Initial Conclusion
Based on all test cases and repeated observations:
The firmware version does not appear to be the root cause.
The issue consistently occurs when using the original Cube Orange+ 64 GB memory card.
The issue does not occur when using the SanDisk 32 GB memory card.
Therefore I’m thinking that , the memory card is the most probable root cause of the issue. I will ran multiple tests to cross verify my observations, and update here accordingly.
Attaching crash_dump.bin when drone booted in case 1 and 2, i was able to get only 1 .bin file
I think you have deduced the issue. We have made some improvements recently that will be in the upcoming 4.7 release, and they will hopefully avoid such catastrophic results when SD card hardware fails.
A partial crash_dump file isn’t super helpful, and I don’t think it’s worth my time to try and parse it, since the root cause appears to have been identified.
