Firmware validation error for board

Blue Robotics Software BlueOS
1

"When flashing the firmware for my BlueROV, I encountered this error: ‘Firmware validation is not implemented for this board yet.’ What is the solution?"Since my flight controller is inside a sealed compartment, I want to flash the firmware via BlueOS.

ce46a1b73f856b79187a4582e6a21575
ce46a1b73f856b79187a4582e6a215751312×1107 118 KB

2

Hi @blueblur, welcome to the forum :slight_smile:

What kind of hardware setup are you using?
I believe BlueOS should be able to flash ArduPilot firmware on most compatible flight controller boards, provided it is connected to the board via USB.

Is it permanently sealed, or oil-filled or something (which makes it extra annoying to open), or is it in one of our water-tight enclosures (or something similar), and you’d just prefer not to open+close it more than necessary?

4

I have successfully connected to the Raspberry Pi via SSH from my laptop. Next, I will attempt to download QGroundControl (QGC) on the Raspberry Pi.

5

Thank you for your assistance. I am using a ​Raspberry Pi ​ and an ​FMUv3 ​ flight controller (detected by BlueOS). Since opening the sealed compartment is inconvenient, I will now try to flash the ArduSub firmware via ​QGroundControl

6

I’ve opened the sealed compartment and found that Mission Planner identifies the board as ​FMUv2 , while BlueOS detects it as ​FMUv3 . After refreshing the bootloader, I was finally able to flash the firmware.

1 Like