Starling not arming
-
Since yesterday, when I turned on the Starling drone, it just sits there. It's not getting armed. When I checked for ADB shell, it's not getting connected, and an error comes up saying no devices found. When I checked the forum, it said it might be bricked due to some file loss. We followed the unbrick tutorial, and after successful flashing of the latest QDL M0054.14.1a-flat-v3, the device is showing up as Qualcomm bulk something. However, ADB still isn't getting connected.
Please note that I am unable to enter adb shell and fast boot mode .For unbrick I followed this
https://docs.modalai.com/voxl2-unbricking/ -
@david-devassy Hi David, we are sorry you are having issues. It does seem like it's bricked. If you follow https://modalai.com/rma you can send it back and we'll see what it would take to bring it back to life.
-
Thanks for the wonderful support from team modal AI. Here is the solution which they have shared with me, which is tested and working 100%.
Please download the attached file
file:
Download thisMove into the ufs sub directory of that release ^:
cd 2024-02-09-1.7.4-M0054-2/ufsSlide the SW2 switch to ON to be in QDL mode
Plug in power and USBRun:
sudo qdl --debug --storage ufs --include . prog_firehose_ddr.elf rawprogram_unsparse0.xml rawprogram1.xml rawprogram2.xml rawprogram3.xml rawprogram4.xml rawprogram5.xml patch0.xml patch1.xml patch2.xml patch3.xml patch4.xml patch5.xml