ADB Connecting Issue with VOXL2 Board

tom

@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.

dlee

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

tom

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

dlee

@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

tom

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

dlee

@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. 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?

tom

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

dlee

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

tom

@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

dlee

@tom I already did QDL flash.

This is what I did.

QDL flash
Voxl2 flash using fastboot mode
Connect to the voxl-suite
After I reboot, adb shell didn't work.
error: no devices/emulators found.

I tried many times of this from 1 to 4.

tom

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

dlee

@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.

tom

@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??

tom

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

dlee

@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.

tom

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

dlee

@tom Removed it. ADB wasn't detected. Do you have some advices my setup?
IMG_6989 Large.jpeg

tom

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

dlee

@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

modaltb

@dlee said in ADB Connecting Issue with VOXL2 Board:

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....

ModalAI Forum

ADB Connecting Issue with VOXL2 Board