Starling Drone not showing up in ADB devices

[ijones2]

@Vinny

[Vinny]

Hi @ijones2
Thanks for those. Your Starling looks like it's new out of the box, so I do not suspect anything severe is happening. All of the green lights when you power I can see in the image stay solid green, right (no flashing/flickering)?
if so, all should be OK and your system is likely booting, so you may have a problem with your host machine.
I am from Hardware, so I'll need to pull in someone from software team to help you.

@tom ,
My suspicion is ADB is not installed correctly on the host machine, but I do not know how to help someone through that.
Or...
If the drone was operating and the battery suddenly dropped out to give the red LED, it just means it was shut down. But, if the shut-down was occurring during a write operation which could have been happening from a QGC config, it might be bricked.
any ideas?

Thanks!

[tom]

@ijones2 When your drone is powered and plugged into your host machine via USB, what do you see with lsusb?

[ijones2]

@Vinny @tom

Yep! Solid green, no flickering!

I tried the unbrick guide but then I got to this step:

Initiate flash
While in the ufs sub-directory of the image release, run the following qdl command in order to flash the device:

$ 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

and it would say waiting for device and I left that on the screen because it said that the qdl flash will take some time. I had to end the process because it was going on 4+ hours of waiting for device. I restarted it and it was still taking hours. I never got to the point of seeing the completion output.

when I would run this $ lsusb the starling would not show up.

[tom]

@ijones2 When you are attempting to use QDL are you flipped the switch to the ON position?

QDL should start giving output instantly so no need to wait that long before trying something else

[ijones2]

@tom

Hey Tom!

I do have the switch flipped on!

[ijones2]

@ijones2 @tom

[tom]

@ijones2 I would try opening a new terminal, running sudo dmesg -wH, then powering and plugging in your VOXL 2 to your host PC and see if you see any enumeration info come through. This will tell us if your cable setup is good

[ijones2]

@tom

Hey Tom!

I ran the code and I got a lot of input but I went and scrolled specifically to the usb part and here's what I got

I can send a picture of all the output it's a lot but let me know if that will be helpful.

[tom]

@ijones2 Can you try without running anything else? Just plugging in the board and powering it on should spit out some messages if it's detected correctly

[ijones2]

@tom

Hey Tom!

Here'd what I got!

[tom]

@ijones2 I'm not seeing any devices that seem to be the drone enumerating. Do you happen to have another machine or USB cable setup you can test with?

[ijones2]

@tom

Hey Tom!

I have ordered another USB-C to USB-A cable and made sure that it included data transfer and should be here tomorrow. The cable I am currently using has/had worked but I am starting to think it might be the cord. I will find out tomorrow when it arrives and will update you then! If the new cords do not work on my lab laptop, I will try the cords on a different PC and if THAT does not work...

[ijones2]

@tom

Hey Tom! i think this is progress?
I tried 3 different USB-C to USB-A cords and the third one gave me " Bus 002 Device 002: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode) "

so I guess it was the cord? Or is it my lab laptop?

I kind of don't know what to make of this??

[tom]

@ijones2 QDL means that the QDL switch is likely switched to ON which would meant that the QDL unbricking process would likely work. Can you try the same test with the switch OFF (requires plugging/unplugging power) and see what lsusb shows?

[ijones2]

@tom

Hey Tom! good news!

I got new cables for the drone now and when I connected the drone it shows up on the lsusb and I am able to run the adb shell. Would I have to unbrick it or because the adb shell is running I would not need to unbrick it? Essentially I'm asking what my next steps should be?

[tom]

@ijones2 This is great news! It looks like everything is functioning as expected so no need to go through the unbricking process at this point.

It does appear that there is a fairly old SDK loaded on there so I would recommend flashing the latest SDK (1.3.3) from downloads.modalai.com under "VOXL 2 Platform Releases"

Just follow the instructions here to do so: https://docs.modalai.com/flash-system-image/#flashing-a-voxl-sdk-release