Open covelus opened 5 months ago
I wonder if this might be related to QGroundControl Crashes with H.265 Stream When AutoConnect is Enabled #11523
This issue has been mentioned on Discussion Forum for PX4, Pixhawk, QGroundControl, MAVSDK, MAVLink. There might be relevant details there:
https://discuss.px4.io/t/pixhawk-6x-rt-cant-connect-to-qgroundcontrol-or-nsh/38499/3
This issue has been mentioned on Discussion Forum for PX4, Pixhawk, QGroundControl, MAVSDK, MAVLink. There might be relevant details there:
Expected Behavior
Having QGroundControl opened, and having accepted location services and incoming connections, I connect through USB the Holybro Pixhawk 6X (rev8) or 6X-RT NXP (Developer Edition), select Firmware and proceed to start update process: unplug the USB as QGC requests, connect it again, select PX4 Pro -> stable version and the stable version of the firmware gets flashed, or an explanatory error gets reported.
Current Behavior
Having QGroundControl opened, and having accepted location services and incoming connections, I connect through USB the Holybro Pixhawk 6X (rev8) or 6X-RT, select Firmware and proceed to start the install process: disconnect the USB as QGC requests, connect, select PX4 Pro -> stable version, once accepted, during the flashing process, the application crashes and closes, with no further information or explanation. Device get apparently and somehow modified, keeping locked or maybe damaged during this process.
Steps to Reproduce:
System Information
Detailed Description
I tried the same process, first a 6X-RT, first with the stable QGC (4.3.0, as mentioned below), then I installed the RC-1 (4.4.0rc1), no changes, then the daily built from around April 2023, and, after no changes, I returned to the stable. I also tested also on Windows the stable release.
No changes, so, I could return the 6x-RT, blaming the alpha firmware it had installed from factory when I received it (1.15.0alhpa Firmware), then I got a 6X, but I see it comes with the same alpha firmware (Screenshot-1), and I am having exactly the same issues... After the first crash with the 6X (rev8), I collected the log (QGC Console Log below) configured the flight controller as Flying Wing, reset the parameters, and rebooted it, just to try options, and tried to repeat again again the process, with the same results.
I also tried to run it from the shell, as documented in QGC documentation, with same results (check QGC Shell-run Log below).
So, wondering if the QGC cannot handle a downgrade (or v.1.15alpha0), and if the crash may have damaged the devices (please, apply a proper exception management policy to QGC, to avoid this issues, this is critical).
Very important, please: I also wonder how to unlock/recover the device.
Log Files and Screenshots
Screenshot-1: Holybro Pixhawk 6X (rev8) as received.
Screenshot-2: Flashing the firmware before the 1st crash
Screenshot-3: Pixhawk 6X Connection after the crash, new banner error on top (and usual warnings from Airwind sensor not yet configured, this is normal.
Screenshots-4: Attempt to flash again both Pixhawks
Previous 6X-RT
This one, afterwards and still 6X-RT, was slightly different, file not found error, but this was not notified before, and a crash happened anyway:
Screenshot-5: Pixhawk 6X SD card content.