Various issues running BlueOS on Pi CM4

[akiUlysses]

Hey all,

My setup is a Holybro P6X running ardusub 4.6.0-dev (bdshot) with a CM4 on their Pixhawk RPi CM4 Baseboard. Internally the autopilot is connected to the CM4 via Serial, Telem2 is connected to the Pi as below:

• CM4 GPIO14 ↔ FMU TXD TELEM2

• CM4 GPIO15 ↔ FMU RXD TELEM2

• CM4 GPIO16 ↔ FMU CTS TELEM2

• CM4 GPIO17 ↔ FMU RTS TELEM2

I’ve used MAVProxy to verify that the serial port communications work ok.

I used the command from the BlueOS install directory to install Blue OS on top of a fresh raspian install - this all seemed to execute flawlessly however I face a few issues now.

1.

I am getting a warning saying that the vehicle is running its factory version of BlueOS, and that means something went wrong how can I find out what is causing this and rectify this? (Cannot upload system logs as I am a new user)

2.

I’m getting a series of continuous errors from “Wifi Manager” - what do these mean and how can I rectify them?

3.

How can I configure Mavlink router to use the /dev/ttyS0 or /dev/serial0 for communicating with the autopilot instead of /dev/ttyACM0? Currently I have to use a usb cable to connect the autopilot to the CM4 for blueOS to see it, even though they are on the same board.

Any and all help is much appreciated!

[tony-white]

Hi @akiUlysses

• Please update both BlueOS and the Bootstrap (afterwards) in order to get rid of the factory version message.
• Those WiFi errors are likely due to you installing BlueOS on top of Raspian, instead of flashing the BlueOS image?
• I think @williangalvani can comment on how to adjust the port for serial communications with your autopilot!

[akiUlysses]

I’m getting the below error trying to update bootstrap, how can I fix the manifest issue? - Fixed, I realised I had to apply a remote version

For deployment reasons, and ability to use BlueOS on other SBCs (Such as Jetson Orin) I am going the docker route and installing BlueOS on top of Raspian, with this setup how can I resove those WiFi Manager errors?

Additionally, I just noticed the below issue, do you know what this means?

Thank you!

[akiUlysses]

@tony-white I’ve been able to fix the wifi manager issues by rectifying the issue with dhcpcd.conf being a directory and not a file. This change doesn’t persist through reboots due to the nature of docker of course so is not a real fix.

Does the install.sh script need to be updated? I tried fresh installs and the same issue occurred so I suspect something is wrong with the docker container being setup and provided or the way I am using it?

Would really appreciate help in fixing this as it actually prevents connection through the tether as the static IP is not working due to the dhcpcd.conf issue.

@williangalvani any advice on adjusting the port used for the PI to communicate with the autopilot via serial instead of USB would be super helpful!