Discussions

Stuck on "ERASING LOGS" during startup

Posted by Dave on January 14, 2012 at 3:26am

Hi All,

Recently my APM board has not been starting up properly. When I connect it to a serial terminal I can see that it get's stuck on:

Init ArduCopter V2.2                                                            
                                                                                
Free RAM: 1343                                                                  
FW Ver: 113                                                                     
----------------------------------------                                        
                                                                                
                                                                                
U3þERASING LOGSÒ?                                                               
Erasing log...                                                                  
+               

Sometimes there's one + and sometimes two or four. It always hangs at that stage, though. I think something could be wrong with the log memory on the board.

Any ideas? It's stopping me flying and it's beautiful weather today :(

Cheers,

Dave

You need to be a member of diydrones to add comments!

Join diydrones

Email me when people reply –
Follow

Replies

  • 3D Robotics
    Chris Anderson February 21, 2012 at 7:08am

    Dave, please update to the latest software (2.4) and try again. 

  • Dave February 21, 2012 at 6:44am

    So I just updated to 2.4 - mistake.

    Now my board does nothing except get to the first startup message and then hangs. I tried rolling back to my custom build and it still doesnt work.

    Anyone got any protips on dealing with a broken eeprom ? Is it time for a new board? :(

  • Don Brooks January 14, 2012 at 4:43am

    I'm guessing this is on a 2560, as logging is forced to disabled on the 1280 and most don't have an APM2 yet?

    Have you tried disabling logging to see if it boots?

    in APM_config.h check for this at the end of the file, remove the comment (//) and set it to DISABLED

    //# define LOGGING_ENABLED

  • Dave January 14, 2012 at 3:27am

    I should point out this was happening on 2.1 alphas as well. It never happened on the old 49 or 50 versions. I don't know how to roll it back, though.

This reply was deleted.

Activity