This issue occurs because newer Cube Orange+ boards require an updated bootloader for PX4 v1.14.x to function correctly. The following workaround has been tested and restores full functionality while remaining within the UAV Toolbox Support Package for PX4 AutoPilots workflow:
Workaround Steps
- Run MATLAB Hardware Setup: Launch the hardware setup screens from MATLAB and, in the Test Connection step, upload the firmware to the Cube Orange+ board. This will upload PX4 v1.14.3 (which is acceptable for this process).
- Close Hardware Setup: Exit the hardware setup screen in MATLAB.
- Open QGroundControl (QGC): Launch QGC and wait for it to connect to the Cube Orange+.
- Update Bootloader via MAVLink Console: In QGC, go to MAVLink Console and run the following command:
bl_update /etc/extras/cubepilot_cubeorangeplus_bootloader.bin
Expected output:
nsh> bl_update /etc/extras/cubepilot_cubeorangeplus_bootloader.bin
INFO [bl_update] image validated, erasing bootloader...
INFO [bl_update] flashing...
INFO [bl_update] verifying...
INFO [bl_update] bootloader update complete
Reboot the Cube Orange+: After reboot, the correct PX4 bootloader will be in place. The board should now work as expected with PX4 v1.14.x and UAV Toolbox Support Package for PX4 AutoPilots.
Why This Works
The newer Cube Orange+ hardware requires an updated bootloader for PX4 v1.14.x. Without this update, RC input, PWM outputs, and certain sensors fail to initialize. Updating the bootloader resolves these issues without requiring an immediate upgrade to PX4 v1.15+.
Additional Notes
- Tested with MATLAB R2024a, R2024b, R2025a & R2025b and PX4 v1.14.3.
- After applying this fix, RC, LiDAR, telemetry, and PWM pins all function normally.