hello;
i uploaded the stable release from QG control.
i can’t figure out how to get the .PX4 firmware (older version) can you help me send the the file for my Cube Orange Plus ?
i think 1.14.0
thanks
hello;
i decided to open the carrier board, and use ETlink and i successfully downloaded the bootloader .hex file to the main mcu, and downloaded the iomcu_bl.bin to IO mcu.
no hope. it’s not showing green ! although its Cube Orange + Mavlink and Cube Orange + SLCAN but it cant connect to mission planner.
i regret buying this device, anyways …
I’m planning to buy the durandal (from hollybro)
do you have any comments on this ? maybe you have another idea …
since day 1 it didn’t work properly, since day 1.
thanks.
updating IO_MCU
@Paul_Fahed I would like to request that you refrain from using hostile remarks on this forum. I understand that it can be quite frustrating trying to resolve issues, but we are here to support as best as we can. And it is not helpful to anyone to bring hostile comments into the mix.
Now getting back to the issue at hand. It is a positive sign that you are able to update IOMCU, this means that hardware itself is ok. You pointed out that Green LED is now off. Can you let me know if the LED is on at boot for few moments and then goes of. If so that again is a positive sign that IO Firmware is loaded and is working. All LEDs are turned of during normal operation to minimise self heating.
I have few more questions since you are able to flash IO MCU:
-
Did you completely erase the entire flash on IO MCU before downloading the bootloader? please do so if you didn’t. If you don’t completely erase, it will still have potentially bad firmware in.
-
When you loaded the bootloader, did you notice rapid RED LED flash for few moments after power cycle and then all LEDs turned off eventually? This is a good sign.
-
Which bootloader file did you use?
-
Inability to connect to USB is indication of something else going on. Even if IOMCU is there, Mission Planner should connect and just complain unable to update IO Firmware. Can you connect a serial terminal on MAVLink COM, like Putty, and see if you get anything there (baudrate not relevant, just connect to USB COM).
Warning: Updating Bootloader manually is fine, But do not manually update the firmware itself on IOMCU. The correct firmware will be loaded by Ardupilot itself. The rapid RED LED flash is a sign of Ardupilot updating firmware.
So far there have been no signs to suggest that hardware itself is faulty. All things indicate that IOMCU was put in a bad state by PX4 Firmware (I couldn’t replicate it on my end, so possibly a corner case in software yet unknown). More than happy to help you recover it.
I would like to request that you refrain from using hostile remarks on this forum. I understand that it can be quite frustrating trying to resolve issues, but we are here to support as best as we can. And it is not helpful to anyone to bring hostile comments into the mix.(no comment)
Now getting back to the issue at hand. It is a positive sign that you are able to update IOMCU, this means that hardware itself is ok. You pointed out that Green LED is now off. Can you let me know if the LED is on at boot for few moments and then goes of. If so that again is a positive sign that IO Firmware is loaded and is working. All LEDs are turned of during normal operation to minimise self heating.(the green led will make a single pulse like 0.5 second then the red led/green side, will flash fast, and the red led/adsb antenna side, will stay red.)
I have few more questions since you are able to flash IO MCU:
-
Did you completely erase the entire flash on IO MCU before downloading the bootloader? please do so if you didn’t. If you don’t completely erase, it will still have potentially bad firmware in.(no i didn’t but i placed it upside down and connect my leads, and perform a full erase and then i installed iomcu_f103_8MHz_bl.bin, then i tried to connect, no hope, i flashed the rover firmware, no hope, but i noticed that the led pattern changed here : a solid green, and a flashing red/green side, for like two seconds, and a fast flashing red/antenna side. i also repeated the process with iomcu_bl.bin same thing. it’s doing the same behavior if you power it on while holding the safety button.
also note that now the safety button is not flashing) -
When you loaded the bootloader, did you notice rapid RED LED flash for few moments after power cycle and then all LEDs turned off eventually? This is a good sign. (no, leds are flashing now the way i just described)
-
Which bootloader file did you use? (for iomcu it’s mentioned above, for the main FMU i used CubeOrangePlus_bl.hex.)
-
Inability to connect to USB is indication of something else going on. Even if IOMCU is there, Mission Planner should connect and just complain unable to update IO Firmware. Can you connect a serial terminal on MAVLink COM, like Putty, and see if you get anything there (baudrate not relevant, just connect to USB COM). (no idea what you are talking about)
Warning: Updating Bootloader manually is fine, But do not manually update the firmware itself on IOMCU. The correct firmware will be loaded by Ardupilot itself. The rapid RED LED flash is a sign of Ardupilot updating firmware.(i dont have the IOmcu firmware, i downloaded those two boot loaders from here : ArduPilot firmware : /Tools/Bootloaders
So far there have been no signs to suggest that hardware itself is faulty. All things indicate that IOMCU was put in a bad state by PX4 Firmware (I couldn’t replicate it on my end, so possibly a corner case in software yet unknown). More than happy to help you recover it.
Finally, I don’t mind spending time discussing my problem, and I apologize for my words. In a moment of frustration, I found myself alone, struggling with my $500 Cube without any support.
thanks.
hello;
now it’s connecting to mission planner ! but the same message “Failed to update io Firmware”
i downloaded the “iomcu_f103_8MHz_bl.bin” (using ST32Cube programmer, the same thing.
led status : solid green led and a fast flashing red/antenna side.
any suggestion ?
Update;
once i started to set the frame parameters, frame class, frame type, i disconnect, remove the usb, then connect it back, doesn’t wants to connect. solid green with fast flashing red/antenna side.
then i used STM32cubeprogrammer again, flashed :
CubeOrangePlus_bl.hex
iomcu_bl.bin
no hope, same led pattern, no connection.
then i flashed the hex firmware with bootloader “arducopter_with_bl.hex (stable version)”
same same.
i will order another one, let’s move on.
@Paul_Fahed the correct firmwares are
arducopter_with_bl.hex
iomcu_bl.bin
Does the solid green and fast flashing red/antenna side ever stop eventually?
I just got my board working after having the same problem. I had arducopter.
I reset to default params and it didnt change, after that i loaded arduplane to the board and it booted succesfully. I then loaded ArduCopter back to the board and it worked correctly.
Hope this works @Paul_Fahed
Let me know if it did
i bought another cube orange from 3DXR, it works like a charm !
i contacted aliexpress seller to give me his address, no reply.
anyway, i’m happy that my copter is flying now, and i guess as the time passes by, i should figure out the problem of the old one. (i’m pretty sure it’s a programing error)