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

    VOXL2 ADB not working

    Ask your questions right here!
    5
    18
    1167
    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.
    • tomT
      tom admin
      last edited by

      @darwin-keem What's the whole output of what it shows up as in lsusb ? It's possible it has been bricked, in which case you will need to use the "QDL" tool in order to get it going again: https://docs.modalai.com/voxl2-qdl/

      D 1 Reply Last reply Reply Quote 0
      • D
        darwin.keem @tom
        last edited by

        @tom This is the full output of lsusb.

        Untitled.png

        1 Reply Last reply Reply Quote 0
        • D
          darwin.keem @Adrian Hidalgo
          last edited by

          @Adrian-Hidalgo We disconnected ToF and reconnected with the original Hi-Res camera. Also, we've checked the camera connections, but had no issue about it. However, we've disconnected GPS module, as we don't need it. Can this be the reason?

          1 Reply Last reply Reply Quote 0
          • D
            darwin.keem
            last edited by

            @tom We've ran factory reset with qdl and this is the output.

            Untitled-2.png

            After performing qdl, if we run lsusb without turning off the power, it gives us this.

            Untitled-3.png

            If we cycle power and run lsusb, it is still shown below. It is not recognized as 05c6:901d.

            Untitled-4.png

            1 Reply Last reply Reply Quote 0
            • tomT
              tom admin
              last edited by

              @darwin-keem After running the QDL flash and removing power did you switch back off the EDL switch on VOXL2 before powering back on?

              D 1 Reply Last reply Reply Quote 0
              • D
                darwin.keem @tom
                last edited by

                @tom Yes, we did.

                1 Reply Last reply Reply Quote 0
                • tomT
                  tom admin
                  last edited by

                  @darwin-keem Did the output of the QDL flash look complete? Did it reach the point seen in this doc: https://docs.modalai.com/Qualcomm-Flight-RB5-QDL/

                  <response value="ACK" rawmode="false" /></data>
                  partition 1 is now bootable
                  FIREHOSE WRITE: <?xml version="1.0"?>
                  <data><power value="reset"/></data>
                  
                  FIREHOSE READ: <?xml version="1.0" encoding="UTF-8" ?>
                  <data>
                  <log value="INFO: Calling handler for power" /></data>
                  LOG: INFO: Calling handler for power
                  FIREHOSE READ: <?xml version="1.0" encoding="UTF-8" ?>
                  <data>
                  <response value="ACK" rawmode="false" /></data>
                  
                  1 Reply Last reply Reply Quote 0
                  • D
                    darwin.keem
                    last edited by

                    @tom Yes, it reached the point. The result is written on the previous replies.

                    1 Reply Last reply Reply Quote 0
                    • tomT
                      tom admin
                      last edited by

                      @darwin-keem Apologies, I missed that reply. Are you able to force the VOXL2 into fastboot via. the button? You can follow this video for instructions: https://www.youtube.com/watch?v=IM3PnW7cipQ

                      1 Reply Last reply Reply Quote 0
                      • D
                        darwin.keem
                        last edited by

                        @tom Yes, entering into fastboot mode is possible. We tried re-flashing with voxl2_platform_1.3.1-0.8/system-image/flash-system-image.sh. But after flashing, it doesn't go after but only waiting for ADB.

                        Done Flashing
                        [--------------------------------------------------------](100%)
                        rebooting...
                        
                        finished. total time: 0.050s
                        [INFO] Waiting for ADB
                        1 Reply Last reply Reply Quote 0
                        • D
                          darwin.keem
                          last edited by darwin.keem

                          We need VOXL 2 to work urgently. Can we get any remote assist? Thanks.

                          Eric KatzfeyE 1 Reply Last reply Reply Quote 0
                          • Eric KatzfeyE
                            Eric Katzfey ModalAI Team @darwin.keem
                            last edited by

                            @darwin-keem This can mean that you have a damaged power cable from the APM to the VOXL 2. The cables are Robotis 184-903-0081-000 Cable-4P if you don't have a spare to try.

                            D 2 Replies Last reply Reply Quote 0
                            • D
                              darwin.keem @Eric Katzfey
                              last edited by

                              @Eric-Katzfey Thanks. We will try as soon as possible. Are there any more possible solutions that might solve this problem?

                              1 Reply Last reply Reply Quote 0
                              • D
                                darwin.keem @Eric Katzfey
                                last edited by

                                @Eric-Katzfey We've tried replacing power cable with a spare. Tried fastboot and qdl again, but it doesn't work.

                                1 Reply Last reply Reply Quote 0
                                • modaltbM
                                  modaltb ModalAI Team
                                  last edited by

                                  @darwin-keem ,

                                  Going through the thread above, a link was provided for the RB5 Flight QDL, but you have a VOXL2 Sentinel.... So for QDL on VOXL 2 the link is: https://docs.modalai.com/voxl2-qdl/

                                  And you should be using these files for the QDL process:

                                  VOXL2 QDL Image 14.1a_1.1.2
                                  r14.1a_1.1.2-M0054-14.1a-FLAT-V3.zip

                                  Can you confirm that is what you have used? This is what we would use as the first step towards troubleshooting as well internally.

                                  What I normally do is remove any hardware connections to the bare minimum if I'm having issues with bootup..... If camera connectors have issues, it can prevent bootup for sure.

                                  D 1 Reply Last reply Reply Quote 0
                                  • D
                                    darwin.keem @modaltb
                                    last edited by

                                    @modaltb Yes, we used r14.1a_1.1.2-M0054-14.1a-FLAT-V3.zip as well.

                                    We will make a try with removing all the hardware connection.

                                    1 Reply Last reply Reply Quote 0
                                    • First post
                                      Last post
                                    Powered by NodeBB | Contributors