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.
Permalink Reply by eduardo on November 28, 2011 at 1:44pm i have the same problem here.
i downgraded firmware do 2.0.50
Permalink Reply by eduardo on November 28, 2011 at 2:04pm well ...i recovered my ardupilot 2.0.52;
go to CLI setup
setup the radio
exit
after this your board will work normal.
Permalink Reply by Christopher Cooper on November 28, 2011 at 3:05pm Thanks for the response, glad it's not just me! Will try this tonight.
Permalink Reply by Ruben Wijnhoven on November 28, 2011 at 11:56pm I am having the same issue with 2.0.53 hangs on erase logs.
Permalink Reply by Christopher Cooper on November 29, 2011 at 3:26am Just installed 2.0.54 and it worked. Problem solved for me.
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.6 members
24 members
249 members
43 members
8 members
© 2013 Created by Chris Anderson.
Powered by
