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

    VOXL2 troubleshooting

    VOXL 2
    3
    14
    421
    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.
    • C
      claw @Moderator
      last edited by 22 May 2025, 19:36

      @Moderator here is a screenshot before and after plugging the usb cable in:

      7eda5c82-560e-4fdb-8e27-11e1904e93d7-image.png

      T 1 Reply Last reply 23 May 2025, 19:54 Reply Quote 0
      • T
        tom admin @claw
        last edited by 23 May 2025, 19:54

        @claw It looks as though the board is booting into fastboot. At this point you should be able to install the voxl2_SDK with ./install.sh

        C 1 Reply Last reply 23 May 2025, 20:18 Reply Quote 0
        • C
          claw @tom
          last edited by 23 May 2025, 20:18

          @tom oh, ok. I thought I'd have adb from the firmware. My mistake. Thanks for the help.

          C 1 Reply Last reply 25 May 2025, 15:59 Reply Quote 0
          • C
            claw @claw
            last edited by 25 May 2025, 15:59

            @tom I tried to install the SDK but it failed.
            I did re-read the instructions for unbricking which do say that ADB should be available after installing the flat build. Is there a mechanism for returning the boards for repair?

            e8165df7-6cf4-4744-8b01-78bf36c921c4-image.png

            T 1 Reply Last reply 27 May 2025, 16:56 Reply Quote 0
            • T
              tom admin @claw
              last edited by 27 May 2025, 16:56

              @claw Can you double check that you're loading the correct QDL image? You'll need to determine whether your board is an M0054-1 or M0054-2

              https://docs.modalai.com/m0054-versions/#m0054-1-and-m0054-2

              C 1 Reply Last reply 27 May 2025, 19:36 Reply Quote 0
              • C
                claw @tom
                last edited by 27 May 2025, 19:36

                @tom i did check that initially and again before I loaded it this last time. We have the older version boards.

                T 1 Reply Last reply 27 May 2025, 19:55 Reply Quote 0
                • T
                  tom admin @claw
                  last edited by 27 May 2025, 19:55

                  @claw Are you running Ubuntu natively? If so, what version?

                  C 1 Reply Last reply 28 May 2025, 16:26 Reply Quote 0
                  • C
                    claw @tom
                    last edited by 28 May 2025, 16:26

                    @tom yes, 22.04

                    T 1 Reply Last reply 28 May 2025, 17:37 Reply Quote 0
                    • T
                      tom admin @claw
                      last edited by 28 May 2025, 17:37

                      @claw I would try installing the SDK with ./install.sh -w to wipe all partitions and start fresh.

                      If that doesn't work it may be worth submitting an RMA: https://www.modalai.com/pages/rma

                      C 1 Reply Last reply 28 May 2025, 18:33 Reply Quote 0
                      • C
                        claw @tom
                        last edited by 28 May 2025, 18:33

                        @tom thank you. I'll give that a shot.

                        C 1 Reply Last reply 28 May 2025, 21:08 Reply Quote 0
                        • C
                          claw @claw
                          last edited by 28 May 2025, 21:08

                          @tom That completed successfully, but still doesn't provide adb. Also, lsusb still shows the fastboot device whereas the other Starlings that are working show a qualcom device.

                          T 1 Reply Last reply 28 May 2025, 21:28 Reply Quote 0
                          • T
                            tom admin @claw
                            last edited by 28 May 2025, 21:28

                            @claw That is definitely not the expected behavior, I recommend going through the RMA process

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