Hi all.
I have an issue.
I have today downloaded and installed latest (stable) version of Mission Planner software and Arduplane 4.3 firmware for Pixhawk Orange Cube.
Once I Connect Orange Cube to PC, I see “Failed to update IO firmware, fix it and than reboot” into Mission Planner Messages.
I am unable to calibrate sensor (accelerometer, compass). Have anyone experienced this problem ? How can I fix ? Thanks
May I ask ,is there any disconnection during firmware upgrade?
Did this issue happend on other firmware(like copter)?
I’m having the same problem with my Cube Orange. I was setting some parameters in Mssion Planner a few days ago and then it suddenly lost connection without any apparent reason and it wouldn’t re-connect. My PC wouldn’t even detect the board when I plugged in via USB and tried to find it in Windows Device Manager “Ports”. After doing some digging I found out that the drivers to connect had gotten messed up somehow. I cleared the drivers in Mission Planner and re-installed and I was able to connect to the Cube in Mission Planner again. But now when I connect it gives me the exact same error message that Enga described in their post above: “Config Error: Failed to update IO firmware”. I’m not sure why or how this whole thing happened considering that I never even tried to update the firmware to begin with. So I’ve tried re-flashing the latest FW (Copter V4.3.4 OFFICIAL) dozens of times, I even tried flashing the other firmwares (Rover, Plane, etc) and it either fails to flash completely, or it successfully flashes but keeps giving the same Config Error message. And when I try to select the frame type that I’m flying (‘X’,‘Y6A’ Hexacopter) it gives the error “Set FRAME_CLASS OR FRAME_TYPE Failed”. I’m running Mission Planner 1.3.79 build 1.3.8375.24878 (43447be8).
I’m completely lost at this point and I’m just trying to figure out if it’s a software/firmware problem, or a hardware failure. Please Help!
Same problem I’m facing any solution please post
I think my Cube Orange Standard may have lost connection during a firmware update because it was doing it’s thing when the Cube suddenly powered off and my PC wouldn’t detect it when plugging it in. Somehow the drivers to be able to connect disappeared. Got drivers fixed and can connect to PC and Mission Planner now, but it consistently gives me the “Failed to Update IO firmware” message when I flash it with the latest version of Copter.
I spoke to one of the Cube developers on Facebook and he suggested sending it back to the retailer that I bought it from for warranty repair/replacement. I tried contacting the retailer but was unable to reach anyone.
Is there a way to recover my Cube if it gets bricked from losing connection during an update? I hope I didn’t just lose $500 lol 
@Atownammo it should not be possible to brick the Cube through firmware update. If its stopped mid firmware update, the Cube will stay in bootloader mode, and can be updated simply by repeating the update process.
The issue you are facing seems to be unrelated to standard firmware update process.
hello;
@sidbh i have the same problem now, the IMUs and Compass are without ID’s… can’t calibrate them.
i flashed the PX4 firmware, it’s working perfectly there… so i don’t think it’s a hardware issue.
what could be the problem with mission planner ?
after flashing PX4, i flashed the arducopter 4.4.4 it connects to mission planner witout problems, but this message : config error : failed to update IO firmware.
thanks.
@Paul_Fahed can you load the latest PX4 firmware back on and see if that’s ok still?
hi, i changed one of the parameters, everything worked fine, i forgot which one, if you are intrested i can search the forum again and bring it out.
hi the parameter was BRD_IO_ENABLE it was set to 1 , i set it Zero, it worked fine, but no PWM signals to my motors !
any solution ?
That’s basically disabling the use of IO module, and that’s why the message disappears. But this will make MAIN Out PWMs to not work, AUX PWMs will still work. My recommendation is to try loading the PX4 firmware back on, and see if the issue is present there as well. It is possible that PX4 firmware loaded IO firmware with bootloader that may not be compatible with Ardupilot. To confirm that’s the case we need to know if PX4 firmware is still functional or not.
sorry for the late reply.
i installed PX4, no weird messages, but no PWM output from mains.
i set main 1 main 2 … check attached pictures. no hope.
i installed arducopter back, same issue.
i don’t know what to do, it’s a big delay !
pls help !
hello;
i noticed something today, i tried to change frame type from X to plus.
once i disconnected/connected the USB cable, it’s not booting, no steady green led, and it can’t connect trough mission planner.
i installed ardurover, then arducopter back, so i can connect back. (then the the frame class will turn back to undefined, then i can select the frame i like)
so no idea if this issue is related.
Hello,
I’m writing to express my disappointment with Orange Cube Plus. I’m currently stranded with nothing to do, just waiting for the unknown. Perhaps an update will be released to solve the problem, but only God knows!
I have another copter with a Pixhawk 2 controller, which is excellent! I was considering detaching it and replacing the Orange Cube Plus with this controller.
Thank you
You are not the first person to discover that you can load a version of PX4 onto any autopilot and find out that the bootloader and the IO Firmware were updated and no longer allow you to load ArduPIlot so I’m sure there is nothing wrong with your Cube. I suggest you look in the wiki and you’ll learn about what you have to do to change the firmware and what software to use to do it. Then read about how to update the bootloader and how to update the IO firmware. It’s all there!
thanks for your reply, i will check wiki and see how to do it.
i’m able to load any ardupilot firmware through mission planner, but the device is not showing green light and it can’t connect, maybe the device is not booting correctly !
i saw this tutorial :
https://ardupilot.org/copter/docs/common-loading-firmware-onto-chibios-only-boards.html
do you see it’s worth do dive into it ?
thanks.
I really do not want to speak for @CraigElder but it seems like you are really blocked.
I would very much encourage you to read and understand this entire page because as is called out in the documentation, this is a destructive operation.
The page you linked has a section about the bootloader (Loading Firmware onto boards without existing ArduPilot firmware — Copter documentation).
the issue is that i can install any ardupilot firmware one my cube orange plus, this procedure is only for blank boards, of boards with other firmware/boot loader installed on it.
i also don’t want to pen my 500$ cube, i’m constructing a sensitive project.
also no clear procedure on how to enter DFU on cube orange+
i’m so upset, no much topics on internet, no good support for such a beautiful peace of engineering.
dommage!
@Paul_Fahed which PX4 firmware did you upload to the Cube? Need to figure out which release is breaking the IO MCU bootloader. To recover it we may need to do build a custom PX4 recovery Firmware, to get it back to original state compatible with Ardupilot.
