ADB not working. No devices detected
-
@tom I am powering the drone with a lipo 14.8v battery.
-
@Kiazoa-Joao What do you see with
lsusb? -
@tom This is all I see. I does not seem to recognize it when it is plugged in.
-
@Kiazoa-Joao Hmm you're right, do you see LEDs come on on the VOXL board when it is powered? Do you have another USB cable / port combo you can experiment with as well?
-
Hi @Kiazoa-Joao
Is your USB cable this gray coiled up one?
That seems to me to be exceptionally long.
We've not usually had issues with cables on VOXL or VOXL-Flight, but do you have a shorter cable?
USB2 is normally enough to see ADB, and USB2 cables can be longer than USB3, but I'm wondering if your cable is a problem. I know VOXL Flight uses a less common (older) USB3 connector, but there are still plenty of cables from USB2-A (or USB3-A) to USB3-MicroB.
Worth a try.
Thanks! -
@Vinny Hi! I tried using a shorter cable, but still. I am using a Linux sub-system on my windows laptop in order to be able to use Ubuntu. Do you think it might not be communicating correctly? I am very new to this.
-
@tom yes I do see the LEDs, and I tried using another cable.
-
Hi @Kiazoa-Joao
Ahhh, yes WSL has issues and cannot fully replicate the environment needed for these platforms.
I am a windows user (hardware team) and the best I can get with WSL is ADB and a few basic shell commands.
The trick with WSL is to use a normal command prompt and try to get ADB over that, then WSL usually can see it... but for some reason, one blocks the other until they both work.
I've found I need to kill and restart the ADB server on both WSL and Command prompt, sometimes a few times, to get WSL to see the ADB device(s).
Longer term, you will need a Linux machine.
We are exploring the option of dual boot PCs in our Hardware lab, so that may be something worth exploring, but WSL will not work long-term and will not work for loading the SDKs. -
@Vinny I see. thank you for explaining that. can you please help me get this trick to work? every time I try the ADB devices command on the normal command prompt, it either says "ADB" not found or "'adb' is not recognized as an internal or external command,
operable program or batch file." -
HI @Kiazoa-Joao
Try installing ADB in your windows environment. Then try to repeat with once you get ADB devices listing in Command prompt, it should appear in WSL. That is what usually works for me.
But I repeat, you will likely not be able to install SDK's... I tried and it instantly fails in WSL. -
@Vinny Thank you so much.
