Just upgraded my quad to 2.0.51 from 2.0.40 (been out of it for a while!). Doing it all through CLI as I can't get the new Mission Planner working in virtualbox.

Anyway when I reboot it after loading the code, in the CLI I get "Firmware change: erasing EEPROM" and then "Erasing log...". How long is this supposed to take? I've let it sit there for at least 10 minutes and it doesn't seem to get past this stage.

Tags: erasing, log

Views: 97

Reply to This

Replies to This Discussion

i have the same problem here.

i downgraded firmware do 2.0.50

well ...i recovered my ardupilot 2.0.52;

 

go to CLI setup

setup the radio

exit

 

after this your board will work normal.

Thanks for the response, glad it's not just me! Will try this tonight.

I am having the same issue with 2.0.53 hangs on erase logs.

Just installed 2.0.54 and it worked. Problem solved for me.

RSS

Social Networking

Contests

Season Two of the Trust Time Trial (T3) Contest has now begun. The fourth round is an accuracy round for multicopters, which requires contestants to fly a cube. The deadline is April 14th.

A list of all T3 contests is here

Advertisement

© 2013   Created by Chris Anderson.   Powered by

Badges  |  Report an Issue  |  Terms of Service