I am getting “Config Error:Failed to update IO Firmware” after flashing Ardupilot V4.2.3 via mission planner and above on my pixhawk cube orange+.I tried booting using safety button,but it did not help.
I am using Here 3+ GPS,all params other than NTF_LED_TYPES have been saved successfully but when I write this param gives me the error :"Set NTF_LED_TYPES Failed.
The GPS is still lighting all the LEDs(purple,yellow,green)
I have same problem with OrangePlus+ after did more 10 good flight, after day, drone returned that msg and nothing is doing more !
I update new firmware, return to my origin firmware, nothing. I think that is internal error !
my problem now is that the cude doesn’t want to connect !
if i install PX4, it runs great, (but without main outputs)
i can’t connect to mission planner !
@paulfa Hello. How is your new orange plus working out? I have the same problems in 2 cubeOrangePlus. Could this be a fault in the new cube orange series? Seems that everyone has the same problem, nothing out of the ordinary then suddanly it gives this error? Seems fishy to me. Never had this problem before with my black cube. Has been working great for 3 years now.
I am myself wondering what to do with the two that I have. I had the same problem as you, strange behaviour, connection problems, then failed to boot (IO error).
If it is a software related error, isnt there a easy fix that can resolve it?
I have always used QGC (have a herelink that is compatible with it), and that error came when using it.
I will let you know if I find out something, and hopefully you can tell me if you find a easy fix for it
I had the same issue with my Holybro Pixhawk 6c mini. I was able to upload PX4 but not the last version of ardupilot (4.5.6).
I had the same message : "Config error: failed to update IO firmware”
Note: only the FMU ACT and FMU B/E leds were off.
I removed the SD card while the board was off, then I turned it on. The FMU B/E LED started to blink. I turned off the board, inserted the SD card again, turned it on and from that moment the error disappeared.