• Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Register
  • Login
ModalAI Forum
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
    • Register
    • Login

    ADB Connecting Issue with VOXL2 Board

    VOXL 2
    6
    35
    2.9k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • D
      dlee @tom
      last edited by dlee 7 Feb 2023, 22:30 7 Feb 2023, 22:29

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

      1 Reply Last reply Reply Quote 0
      • T
        tom admin
        last edited by 7 Feb 2023, 22:33

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

        1 Reply Last reply Reply Quote 0
        • D
          dlee
          last edited by 7 Feb 2023, 23:11

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

          1 Reply Last reply Reply Quote 0
          • T
            tom admin
            last edited by 7 Feb 2023, 23:33

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

            1 Reply Last reply Reply Quote 0
            • T
              tom admin
              last edited by 7 Feb 2023, 23:34

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

              D 1 Reply Last reply 8 Feb 2023, 00:46 Reply Quote 0
              • D
                dlee @tom
                last edited by dlee 8 Feb 2023, 00:46 8 Feb 2023, 00:46

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

                1 Reply Last reply Reply Quote 0
                • T
                  tom admin
                  last edited by 8 Feb 2023, 17:36

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

                  D 1 Reply Last reply 13 Feb 2023, 19:52 Reply Quote 0
                  • D
                    dlee @tom
                    last edited by 13 Feb 2023, 19:52

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

                    1 Reply Last reply Reply Quote 0
                    • T
                      tom admin
                      last edited by 13 Feb 2023, 20:54

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

                      D 1 Reply Last reply 13 Feb 2023, 22:32 Reply Quote 0
                      • D
                        dlee @tom
                        last edited by 13 Feb 2023, 22:32

                        @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
                        
                        
                        1 Reply Last reply Reply Quote 0
                        • M
                          modaltb ModalAI Team
                          last edited by 14 Feb 2023, 16:33

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

                          D 1 Reply Last reply 14 Feb 2023, 18:16 Reply Quote 0
                          • D
                            dlee @modaltb
                            last edited by 14 Feb 2023, 18:16

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

                            V 1 Reply Last reply 15 Feb 2023, 04:59 Reply Quote 0
                            • M
                              modaltb ModalAI Team
                              last edited by 15 Feb 2023, 01:39

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

                              1 Reply Last reply Reply Quote 0
                              • V
                                Vinny ModalAI Team @dlee
                                last edited by 15 Feb 2023, 04:59

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

                                1 Reply Last reply Reply Quote 0
                                22 out of 35
                                • First post
                                  22/35
                                  Last post
                                Powered by NodeBB | Contributors