Pixhawk 6X Not Detected by BlueOS on CM4 Baseboard

Blue Robotics Software BlueOS
,
1

Hello Blue Robotics Team,

We are trying the Holybro Pixhawk 6X connected to an RPi CM4 baseboard running BlueOS.

We are facing an issue where BlueOS does not detect the Pixhawk 6X when booted on the CM4 baseboard. However, when the same Pixhawk 6X is connected to a standard Raspberry Pi 4, it is detected correctly by BlueOS.

This indicates that the Pixhawk itself is functioning properly, but the issue may be related to the CM4 baseboard USB/UART interface or BlueOS configuration.

We would like to know:

  • Is Pixhawk 6X officially supported with a CM4 baseboard + BlueOS setup?

  • Are there any hardware jumpers, USB routing, or power configurations required on the CM4 baseboard?

  • Do we need to modify any BlueOS settings, udev rules, or device mappings for internal Pixhawk connections?

  • Is any code or configuration change required to enable Pixhawk detection on CM4-based systems?

Any guidance or reference documentation would be very helpful.

Thanks,
Sakthi

2

Its my experience that the Pixhawk6X appears at /dev/serial0on the compute module 4. My digging around in the BlueOS source suggests it never looks on that device for the flightcontroller and so you will need to connect it via the usb bus (which causes it to show up at /dev/ttyAMAx) for BlueOS to see it. An earlier thread discussing this is here Various issues running BlueOS on Pi CM4?

1 Like
3

In my case /dev/serial0 not appears, Is any para value need to change or in raspberry pi or docker need to do any changes ?

What OS you used blueOS or RPI OS and docker pull ?

4

The holybro CM4 is wired a certain way, that - along with the OS you are using - determines what dev file represents the connection. You can’t change the hardware wiring. On mine, with Raspabarian, it appears at dev/serial0. I haven’t got my BlueOS CM4 setup to be able to tell you what it appears as there. I am fairly confident that BlueOS only checks the 4 external USB ports (/dev/ttyAMAX) though, which makes me pretty confident it won’t find it without changes to BlueOS.

2 Likes