I’m trying to upload the latest version of ArduRover (4.5.6) to a Cube Orange+ that’s connected to the BlueOS Pi via USB.
I could plug my laptop directly into the Cube Orange, but it’s in a difficult to access spot so doing this remotely via BlueOS would be ideal.
When starting the firmware upload, BlueOS immediately stops receiving heartbeats from the autopilot (presumably a reboot to enter bootloader?) and then BlueOS throws FETCH_FAIL errors until the firmware upload times out.
Hi @SubseaLED,
I did end up uploading it via Mission Planner.
The firmware I was trying to upload via BlueOS is the latest stable version of ArduRover that it pulled from the database which is for the Cube Orange+.
The reason I would prefer to use BlueOS is so I can do the firmware upload remotely as the autopilot is mounted in a water-tight enclosure inside the vessel hull which makes it a pain to access.
@Nubbish i had some issue similar to yours few months ago when upgrading a pixhawk from 4.1 to 4.5 (ArduSub DEV) through Blueos. It worked only connecting the pixhawk through the USB to the Qground PC.
What’s your actual version on the Qube and the new version you’re trying to install?
@SubseaLED Interesting. The Cube was running Rover 4.5.2 before, and I was trying to upgrade to Rover 4.5.6 (stable).
I did the upgrade via USB with Mission Planner on a PC without issue (except the time and effort to get at the autopilot).
Try to downgrade to the 4.5.5 and upgrade again to 4.5.6 through Blueos. If you still have easy access to the hardware if anything goes wrong of course.
I do not have access to the pc right now to check the files but from the release note seems that no critical changes have been made from the 4.5.2.
