Discussions

Unable to upload firmware on Pixhawk stuck on "attempting to reboot COM4"

Posted by Israel Casillas on August 7, 2015 at 3:25pm

Howdy,

So yesterday everything was working fine and I was able to properly upload the firmware using eclipse, but today it is giving me problems. When I make the firmware and it asks for me to connect the pixhawk it detects everything like normal, but once it reaches this part it freezes and doesn't do anything.
All done!
make[2]: Entering directory `/c/px4/Firmware/Build/px4fmu-v2_default.build'
Loaded firmware for 9,0, size: 879960 bytes, waiting for the bootloader...
If the board does not respond within 1-2 seconds, unplug and re-plug the USB connector.
attempting reboot on COM4...
if the board does not respond, unplug and re-plug the USB connector.
Now I'm not sure what could have caused this. I can still connect to the pixhawk and use its commands through mission planner, but now once I disconnect from mission planner, the main LED turns a solid blue, which I do not remember ever happening.
So, I attempted to update the bootloader this morning. I copied the current bootloader file to the SD card, and I attempted to connect to the pixhawk using Mission planner. Unfortunately, it now seems that I can't even connect to mission planner, it is unable to open the COM4 port at 57600. I also connect the buzzer and once I connect the pixhawk to my computer through the USB port, the main LED flashes red, the buzzer does the following sounds.
beep beep beep BEEEEP, after this point it just continues to hiss
some times it doesn't make it to the last deeper and longer beep, some times it doesn't even beep at all, after this point the FMU B/E LED starts rapidly flashing orange which would indicate that the bootloader is active. 
After this, I have no idea what happened or what I did, and now the pixhawk was except for the pixhawk still not uploading the new code. My computer still recognizes it on COM4, and I am now able to connect using mission planner. The FMU B/E LED is no longer flashing orange it is off, the main LED is now flashing red as before, and it is always able to compete the initial 4 beeps. I attempted to load the new firmware and I was back at my original problem

Now I can't connect to the pixhawk through USB to update the bootloader, I can't update firmware and I still don't know what to do.
Can someone help me out here?
Thank you for the help!

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

Join diydrones

Email me when people reply –
Follow

Replies

  • Kevin Pan January 28, 2018 at 10:31pm

    Well,I have the same problem.Every time I try to upload the firmware to my pixhawk,it says 'waiting for bootloader' as the same.Have you solved it now?

  • Admin
    Thomas J Coyle III August 13, 2015 at 8:41am

    @Israel,

    Communication over the USB connection is done at 115000 baud and not 57600 baud.

    Regards,

    TCIII AVD

    • Israel Casillas > Thomas J Coyle III August 13, 2015 at 8:46am

      Thanks for the reply, Thomas.

      I've tried both 115000 and 57600, but no luck so far.

      Best Regards,

      Israel Casillas

  • Israel Casillas August 13, 2015 at 8:13am

    Ok. I went ahead and looked at the bootlog, and it just has this:

    PX4IO CRC OK 
    PX4IO CRC OK 
    PX4IO CRC OK 
    PX4IO CRC OK 
    PX4IO CRC OK 
    PX4IO CRC OK 
    PX4IO CRC OK 
    PX4IO CRC OK 
    PX4IO CRC OK 
    PX4IO CRC OK 
    PX4IO CRC OK 
    PX4IO CRC OK 
    PX4IO CRC OK 
    PX4IO CRC OK 
    PX4IO CRC OK 
    PX4IO CRC OK 
    PX4IO CRC OK 
    PX4IO CRC OK 
    PX4IO CRC OK 
    PX4IO CRC OK 
    nothing else. When I connect the pixhawk with my computer it gives the proper start up sound, it then goes and flashes red and blue, and finally it stops at 2 yellow flashes, which indicate an arming error. I try to connect to mission planner using the NSH command line, and it get stuck on waiting for reboot, it finally gets to opened COM port, and it freezes there. It does nothing until I disconnect. When I try connecting to the Mavlink, it just states "trying to connect" and counts down. after the countdown is over, it states "No Hearthbeat packets Received". Which is weird because my blue IO light indicates that the heartbeat loop is running. 
    After this 

    I went ahead and changed the Baum rate on my COM4 port, which was set to 9600, to 57600. Now when I attempt to connect I do not get the "no heartbeat packets received" instead I get this:

    I little progress, but I'm not sure what to do.
    Any ideas?
    Redirecting
This reply was deleted.

Activity