Open shazib2t opened 3 years ago
Even I'm facing the same issue. I've tried it out on 3 Cube Oranges so far, 2 are CubeBeta Tester units from 2019 and one is from a couple months ago purchased from 3DXR. I also tested with a Cube Black and PX4 installs and boots up without issues.
So this seems to be specific to the Cube Orange. Also, when the PX4 firmware is loaded the orange light remains lit and does not go out (stuck on the bootloader?). This is not the case when the ArduPilot firmware is loaded.
I can reload ArduPilot without any issues and connect to the board normally. Only facing this issue with the PX4 firmware loaded. The firmware is loading onto the board, but doesn't seem to be booting up. The issue persists with Stable, Beta and Developer (master) versions of PX4.
I have not had issues installing the PX4 firmware file using Mission Planner's "Load custom firmware" option. Even then the result is the same, the orange light remains lit.
I earlier came across a thread here with similar problems, which then led me to #9215, and was going to raise an issue after I faced the same problem with all 3 Cube Oranges when I came across this issue.
Device manager with ArduPilot installed on the Cube Orange (orange light is off):
Device manager with PX4 installed on the Cube Orange (orange light is on):
QGC detects when board is connected, but "Connected to bootloader:" is empty:
QGC after the firmware is installed:
@arunabha42 and All, I am not sure anymore whether this is a QGC related problem or this is a px4 firmware issue for cube orange anymore but with some hacks, I was able to load the firmware and booted the Cube Orange with PX4. So for the cube to work, I modified 2 sections of the px4 firmware but I am not quite sure which one worked. So please give it a try and let us know.
/PX4-Autopilot/boards/cubepilot/cubeorange/init/rc.board_mavlink
mavlink start -d /dev/ttyACM0
I commented on this line to not start for now.
and for second change
PX4-Autopilot/boards/cubepilot/cubeorange/src/hw_config.h
define BOOTLOADER_DELAY 5000
I increased the delay time to 8000 to load with more delay. Next, you have to make cubepilot_cubeorange
and upload the modified .px4 file. After the upload cube orange booted normally and I was able to load the firmware again which worked out nice since in the previous steps I was not starting the MAVLINK in the /dev/ttyACM0.
As similar to this issue 9215 I would like to upload the PX4 stack to my Cube Orange, unfortunately without success. Cube hangs after the successful upload and is stuck at bootloader
I am having the same issue with Cube orange for PX4 firmware load. Qgroundcontrol Daily Build does not solve the issue. I even tried QGC daily build in windows and Linux systems. Tried to upload the firmware using the
make
command but no luck after uploading. Seems like cube orange is stuck in the bootloader loop. Only works with Arducopter firmware.System Information
Log Files and Screenshots
[QGC Console Logs]
Screenshots of QGC
Log from dmesg