Discussions

Since a week orso my copter has trouble getting started.  It would only initialise after many powerup attempts.  Staring in CLI would go fine, in flightmode it would'nt initialise.

After suspecting, gps, barometer and wireless telemetry port, I found the likely cause yesterday : dataflash log.  I put serial.println commands in the init_ardupilot() function to see where it would hang.

It hangs at the start_new_log(); function.

I commented out that function and it works fine.  Also if I disable logging all together it works fine.

DataFlash.Init(); function also seems to work fine, it always hangs at start_new_log().

I wanted to try erasing the datalog (maybe a corrupt log could do this ?) but I found that when I typed "logs" in CLI, the apm would also hang.

I haven't erased logs in quite a while and upgraded multiple firmwares without erasing logs.  There must be quite a bit of logs inthere from different firmwares, certainly with the many startups I do when testing.  Could this cause the above behaviour or is my dataflash toast ?

Is there any way to "unbrick" or format or erase my datalog or otherwise reset it ?

I don't really need the dataflash for flying, but it's incredibly handy for testing and understanding what goes on with the copter.