# ADB Connecting Issue with VOXL2 Board

Source: https://forum.modalai.com/topic/1777/adb-connecting-issue-with-voxl2-board
Category: VOXL 2 and VOXL 2 Mini (https://forum.modalai.com/category/26/voxl-2-and-voxl-2-mini)
Tags: voxl-2
Posted: 2023-02-04 02:03:02 UTC by dlee
Replies: 34 · Views: 8310

## dlee · 2023-02-04 02:03:02 UTC

Hi,

I am currently trying to develop software using the VOXL2 board, but I have run into a roadblock with connecting the board to my computer using ADB. After flashing the VOXL suite, the board got stuck at "waiting for ADB." I have tried several troubleshooting steps, including factory resetting with QDL and changing cables, but the problem persists.

Additionally, during the installation process, the VOXL2 board was unable to switch from fastboot to ADB mode. To resolve this, I divided the shell script into two parts: system-image and VOXL-suite. Although this allowed for a successful installation, the ADB connection problem has resurfaced.

If anyone has any suggestions or solutions for this issue, I would greatly appreciate your help. I am open to trying any and all troubleshooting steps to get this resolved.

Thank you for your time and assistance.

## Reply by Chad Sweet (ModalAI staff) · 2023-02-06 19:41:15 UTC

Hopefully you are following the handling instructions and used ESD protection when handling the PCB? https://modalai.com/handling

## Reply by dlee · 2023-02-06 23:14:29 UTC (in reply to Chad Sweet)

@Chad-Sweet Yepp, I followed ESD protection when handling the PCB. It worked few times only after flashing. But some times after, ADB connection didn't work. New voxl2 board and other board got a same problem. Do you have any solution?

## Reply by Adrian Hidalgo (ModalAI staff) · 2023-02-06 23:16:15 UTC

@dlee What steps were done before the board wouldn't ADB? Did the board go through the whole flashing procedure before "waiting for ADB"? What we've seen is after a hard reset, the fast boot switch on the Voxl2 needs to be pushed for either 25 seconds or boot the board holding the button down for 4 seconds. If you've already attempted this, what was the outcome?

## Reply by dlee · 2023-02-06 23:39:44 UTC (in reply to Adrian Hidalgo)

@Adrian-Hidalgo The board went through the whole flashing procedure. I checked the voxl-suite is running. So I did my works. But after reboot, voxl2 adb couldn't connet to my companion pc.

## Reply by tom (ModalAI staff) · 2023-02-06 23:43:17 UTC

@dlee What OS are you running on your host PC? (We recommend Ubuntu 18)

## Reply by Adrian Hidalgo (ModalAI staff) · 2023-02-06 23:46:56 UTC (in reply to dlee)

@dlee what's the output if you type

```
lsusb
```

## Reply by dlee · 2023-02-07 00:03:19 UTC (in reply to Adrian Hidalgo)

@Adrian-Hidalgo This is the output. 

![c90e600c-597e-4eae-aeca-9f056606eee6-image.png](https://forum.modalai.com/assets/uploads/files/1675728176817-c90e600c-597e-4eae-aeca-9f056606eee6-image.png)

@tom And I am using ubuntu 20.04. It worked before well.

## Reply by tom (ModalAI staff) · 2023-02-07 00:16:45 UTC (in reply to dlee)

@dlee This is with VOXL2 powered and plugged in via. USB-C? Are you running Ubuntu natively or in a VM?

## Reply by dlee · 2023-02-07 00:19:06 UTC (in reply to tom)

@tom Yepp, powered by power adapter. ADB connected by USB-C. Ubuntu natively, not VM.

## Reply by tom (ModalAI staff) · 2023-02-07 01:08:19 UTC

@dlee What do you see come through when you run `dmesg -wH`, then plug in power and USB to VOXL2.

It also doesn't hurt to try a different port on your host PC, i.e. going from USB3 to USB2

## Reply by dlee · 2023-02-07 01:17:57 UTC (in reply to tom)

@tom Nothing changed. I did USB-C and USB-B(3.0), already.

## Reply by tom (ModalAI staff) · 2023-02-07 01:24:37 UTC

@dlee If nothing changed it's likely a cable or port issue. If there's LEDs going on VOXL2 when powered then it is booting.

## Reply by dlee · 2023-02-07 01:38:59 UTC (in reply to tom)

@tom I changed port and cables. It didn't work, too. I tried everything.

## Reply by tom (ModalAI staff) · 2023-02-07 17:37:34 UTC

@dlee Is it detected when forced into emergency boot mode via. the switch? Or can you force it into fastboot via. the button?

## Reply by dlee · 2023-02-07 18:28:31 UTC (in reply to tom)

@tom I did flashing and QDL, again. Re-flashing was successful. But when I reboot it, connection problem occur. I checked status using `dmesg -wH` and `lsusb`. This is the output.

`lsusb`

```
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 018: ID 05c6:901d Qualcomm, Inc. QUSB_BULK_SN:73AD68FF
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 0c45:6a09 Microdia Integrated_Webcam_HD
Bus 001 Device 002: ID 8087:0029 Intel Corp. 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

```

`dmesg -wH`
```
[Feb 7 10:07] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
[  +9.642102] wlp4s0: deauthenticating from e6:f5:32:36:39:23 by local choice (Reason: 3=DEAUTH_LEAVING)
[Feb 7 10:08] wlp4s0: authenticate with 5e:5b:69:67:36:b5
[  +0.007679] wlp4s0: send auth to 5e:5b:69:67:36:b5 (try 1/3)
[  +0.149577] wlp4s0: authenticate with 5e:5b:69:67:36:b5
[  +0.000009] wlp4s0: send auth to 5e:5b:69:67:36:b5 (try 1/3)
[  +0.002812] wlp4s0: authenticated
[  +0.006113] wlp4s0: associate with 5e:5b:69:67:36:b5 (try 1/3)
[  +0.006320] wlp4s0: RX AssocResp from 5e:5b:69:67:36:b5 (capab=0x431 status=0 aid=2)
[  +0.021818] wlp4s0: associated
[  +0.086613] wlp4s0: Limiting TX power to 30 (30 - 0) dBm as advertised by 5e:5b:69:67:36:b5
[  +0.072842] IPv6: ADDRCONF(NETDEV_CHANGE): wlp4s0: link becomes ready
[Feb 7 10:09] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
[Feb 7 10:17] usb 2-1: USB disconnect, device number 9
[Feb 7 10:19] xhci_hcd 0000:05:00.3: Timeout while waiting for setup device command
[  +5.375225] xhci_hcd 0000:05:00.3: Timeout while waiting for setup device command
[  +0.207982] usb 2-1: device not accepting address 10, error -62
[ +11.183109] usb 2-1: new SuperSpeed Plus Gen 2x1 USB device number 12 using xhci_hcd
[  +0.025567] usb 2-1: New USB device found, idVendor=05c6, idProduct=901d, bcdDevice= 0.00
[  +0.000008] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  +0.000002] usb 2-1: Product: QUSB_BULK_SN:73AD68FF
[  +0.000002] usb 2-1: Manufacturer: Qualcomm CDMA Technologies MSM
[  +0.000001] usb 2-1: SerialNumber: 8cc63c2c
[Feb 7 10:20] usb 2-1: USB disconnect, device number 12
[ +19.466698] xhci_hcd 0000:05:00.3: Timeout while waiting for setup device command
[  +5.375457] xhci_hcd 0000:05:00.3: Timeout while waiting for setup device command
[  +0.207938] usb 2-1: device not accepting address 13, error -62
[ +11.099012] usb 2-1: new SuperSpeed Plus Gen 2x1 USB device number 15 using xhci_hcd
[  +0.026684] usb 2-1: New USB device found, idVendor=05c6, idProduct=901d, bcdDevice= 0.00
[  +0.000013] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  +0.000005] usb 2-1: Product: QUSB_BULK_SN:73AD68FF
[  +0.000003] usb 2-1: Manufacturer: Qualcomm CDMA Technologies MSM
[  +0.000003] usb 2-1: SerialNumber: 8cc63c2c
[Feb 7 10:22] usb 2-1: USB disconnect, device number 15
[ +25.073739] xhci_hcd 0000:05:00.3: Timeout while waiting for setup device command

[  +5.375419] xhci_hcd 0000:05:00.3: Timeout while waiting for setup device command
[  +0.208126] usb 2-1: device not accepting address 16, error -62

```

## Reply by tom (ModalAI staff) · 2023-02-07 20:09:08 UTC

@dlee Are you able to force it into fastboot with the button?

## Reply by dlee · 2023-02-07 21:14:09 UTC (in reply to tom)

@tom I can use fastboot mode above the board.
And I got a different problem another voxl2 board (I have 3 of voxl2 boards) [video link](https://youtu.be/XVKtPAu0Pt4). When I connected board to my companion pc using adb cable, the connection is maintained for a very short time and disconnected. Do you know about this problem?

## Reply by tom (ModalAI staff) · 2023-02-07 21:22:41 UTC

@dlee I haven't seen that behavior before. Try `adb kill-server` then `adb shell` again

## Reply by dlee · 2023-02-07 22:04:25 UTC (in reply to tom)

@tom Same. Anyway, can I do something using fastboot?

## Reply by tom (ModalAI staff) · 2023-02-07 22:08:15 UTC

@dlee Yes, that is how the system image is flashed, which is required after a QDL flash. See here: https://docs.modalai.com/platform-releases/#4-run-install-script

The install script can be run while the board is in fastboot mode. Look for it with `fastboot devices`

## Reply by dlee · 2023-02-07 22:29:03 UTC (in reply to tom)

@tom I already did QDL flash.

This is what I did.
1. QDL flash
2. Voxl2 flash using fastboot mode
3. Connect to the voxl-suite
4. After I reboot, adb shell didn't work. 
`error: no devices/emulators found`.

 I tried many times of this from `1` to `4`.

## Reply by tom (ModalAI staff) · 2023-02-07 22:33:45 UTC

@dlee In that case I would RMA it as that is not normal behavior: https://www.modalai.com/pages/rma

## Reply by dlee · 2023-02-07 23:11:44 UTC

@tom One more question. Since we have three VOXL2 boards behaving the same way can we buy one RMA (PCB) diagnostic for all three boards or do we have to purchase a RMA (PCB) diagnostic for each board that is faulty? 

Thanks.

## Reply by tom (ModalAI staff) · 2023-02-07 23:33:45 UTC

@dlee I didn't realize all 3 were exhibiting this behavior, if that's the case something else is going on.

What system image and voxl-suite are you flashing on top of the QDL image? Are you loading or running anything else on top of that??

## Reply by tom (ModalAI staff) · 2023-02-07 23:34:46 UTC

@dlee Do you have anything plugged in to your VOXL2s? cameras? modems? add-on boards, usb devices etc.?

## Reply by dlee · 2023-02-08 00:46:01 UTC (in reply to tom)

@tom I plugged microhard module to use station wifi on voxl (not in microhard). But when I detach the microhard modem, it still didn't work.

## Reply by tom (ModalAI staff) · 2023-02-08 17:36:08 UTC

@dlee Remove the microhard modem and anything else you have plugged in. Does it then allow you to stay in ADB?

## Reply by dlee · 2023-02-13 19:52:21 UTC (in reply to tom)

@tom Removed it. ADB wasn't detected. Do you have some advices my setup?
![IMG_6989 Large.jpeg](https://forum.modalai.com/assets/uploads/files/1676317939180-img_6989-large.jpeg)

## Reply by tom (ModalAI staff) · 2023-02-13 20:54:44 UTC

@dlee I would plug in USB-C and see what  `dmesg -wH` shows

## Reply by dlee · 2023-02-13 22:32:15 UTC (in reply to tom)

@tom This is the result of `dmesg -wH`
```
[Feb13 02:49] audit: type=1326 audit(1676326229.184:214): auid=1000 uid=1000 gid=1000 ses=3 subj=snap.slack.slack pid=1571188 comm="slack" exe="/snap/slack/68/usr/lib/slack/slack" sig=0 arch=c000003e syscall=92 compat=0 ip=0x7f40dea483b7 code=0x50000
[Feb13 03:02] audit: type=1326 audit(1676326970.794:215): auid=1000 uid=1000 gid=1000 ses=3 subj=snap.slack.slack pid=1571188 comm="slack" exe="/snap/slack/68/usr/lib/slack/slack" sig=0 arch=c000003e syscall=92 compat=0 ip=0x7f40dea483b7 code=0x50000
[Feb13 03:05] audit: type=1326 audit(1676327178.011:216): auid=1000 uid=1000 gid=1000 ses=3 subj=snap.slack.slack pid=1571188 comm="slack" exe="/snap/slack/68/usr/lib/slack/slack" sig=0 arch=c000003e syscall=92 compat=0 ip=0x7f40dea483b7 code=0x50000
[Feb13 03:06] audit: type=1326 audit(1676327247.035:217): auid=1000 uid=1000 gid=1000 ses=3 subj=snap.slack.slack pid=1571188 comm="slack" exe="/snap/slack/68/usr/lib/slack/slack" sig=0 arch=c000003e syscall=92 compat=0 ip=0x7f40dea483b7 code=0x50000
[Feb13 03:07] audit: type=1326 audit(1676327271.040:218): auid=1000 uid=1000 gid=1000 ses=3 subj=snap.slack.slack pid=1571188 comm="slack" exe="/snap/slack/68/usr/lib/slack/slack" sig=0 arch=c000003e syscall=92 compat=0 ip=0x7f40dea483b7 code=0x50000
[Feb13 03:09] xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
[  +5.375697] xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
[  +0.207848] usb 2-2.1: device not accepting address 26, error -62
[Feb13 03:10] usb 2-2.1: new SuperSpeed USB device number 28 using xhci_hcd
[  +0.027777] usb 2-2.1: New USB device found, idVendor=05c6, idProduct=901d, bcdDevice= 0.00
[  +0.000016] usb 2-2.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  +0.000007] usb 2-2.1: Product: QUSB_BULK_SN:73AD68FF
[  +0.000006] usb 2-2.1: Manufacturer: Qualcomm CDMA Technologies MSM
[  +0.000005] usb 2-2.1: SerialNumber: 8cc63c2c

```

## Reply by modaltb (ModalAI staff) · 2023-02-14 16:33:19 UTC

@dlee said in [ADB Connecting Issue with VOXL2 Board](/post/8432):
> QUSB_BULK_SN:73AD68FF

When VOXL2 is showing up as `QUSB_BULK_*` in USB devices it means it's in emergency download (EDL) mode.

It goes into EDL mode:
- if the EDL switch (SW2) is "ON"
- VOXL2 fails to boot normally do to an error

If the error is recoverable, using QDL resolves SW/flash related issues.  If after using QDL to reflash, and turning SW2 back off, the VOXL2 continues to boot into EDL mode, in my experience there's possible HW damage that is causing bootup to fail....

## Reply by dlee · 2023-02-14 18:16:15 UTC (in reply to modaltb)

@modaltb If HW was damaged, Can I get RMA service?

## Reply by modaltb (ModalAI staff) · 2023-02-15 01:39:04 UTC

Hi @dlee information on the RMA process is here : https://www.modalai.com/pages/rma

## Reply by Vinny (ModalAI staff) · 2023-02-15 04:59:43 UTC (in reply to dlee)

Hi @dlee 
Can you please double check SW2. From that photo you posted, it seems as if it may stay be in the "ON" position, which would keep it in "EDL" mode and show up as "QUSB_BULK..." instead of an ADB debug device.
Please be sure to follow this step carefully when performing QDL updates:
https://docs.modalai.com/voxl2-qdl/
![e7393327-f780-48b8-8b20-4c18a36639ff-image.png](https://forum.modalai.com/assets/uploads/files/1676437032805-e7393327-f780-48b8-8b20-4c18a36639ff-image.png) 
We do not have many HW failures on Voxl2 in the field from routine use, so to have one so soon is surprising. However, if you are confident you are following all instructions and still wish to RMA it, we'll test it again to check for all basic functionality and debug the root cause of the failure, if any, and prompt you for further actions. 
Thanks!