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

    Sentinel (VOXL2) not booting/not flashing

    Sentinel
    4
    17
    538
    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

      @Andre-Moura Did you accidentally flip the QDL switch on either the VOXL2 or an add-on board?

      A 1 Reply Last reply Reply Quote 0
      • A
        Andre Moura @tom
        last edited by Andre Moura

        @tom Definitely not on the VOXL 2, I checked it beacause of the output of lsusb that I showed previously.
        Add-on board? Is there another switch on the 5G board or one of the Sentinel boards? I think that is a very unlikely scenario, the drone was working one day and the next it wasn't, without any changes.

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

          @Andre-Moura Some of our add-on boards in the past had the same switch on it but it would be obvious.

          If it's still booting into QDL mode, then I would try the QDL tool again. Looking at the output you posted it doesn't look like it ran successfully. I would try again when you get a chance, maybe with another cable or USB port.

          A 1 Reply Last reply Reply Quote 0
          • A
            Andre Moura @tom
            last edited by

            @tom I tried it extensively with different cables/ports/computers during today with no result.

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

              @Andre-Moura Okay, then I'd recommend an RMA: https://www.modalai.com/pages/rma

              J 1 Reply Last reply Reply Quote 0
              • J
                JoshRebello @tom
                last edited by JoshRebello

                @tom Hello,

                My issue is very similar to this, getting the same output as above when I perform the 'initiate flash' sequence.
                My drone was working fine and now when I try to use it again it's having the same issue where 'adb' doesn't detect it. Only for me it wasn't a next day issue, I haven't used my Sentinel for a few months as I was caught up with other projects. Now al of a sudden it won't connect at all.

                Just wanted to know how this was resolved? Want to avoid the RMA if possible as it will be difficult for us.
                Everything suggested so far in this post has been attempted, still facing the issue. Also the errors are exactly similar to what @Andre-Moura faced. Only using batteries provided by ModalAI as well.

                Cheers,
                Joshua

                tomT 1 Reply Last reply Reply Quote 0
                • J JoshRebello referenced this topic on
                • tomT
                  tom admin @JoshRebello
                  last edited by

                  @JoshRebello If you run lsusb or sudo dmesg -wH on your host PC do you see the device enumerating when plugged in?

                  1 Reply Last reply Reply Quote 0
                  • J
                    JoshRebello @Andre Moura
                    last edited by

                    @Andre-Moura Hi Andre,

                    Just reaching out in case you get this. I'm currently facing the exact same issue you had with your sentinel, the same as in this thread. Done all the checks similar to what was posted in this thread got the exact same results as you as well - so I'm assuming it is the same issue that you had.

                    I've been asked to do an RMA but I wanted to check if there was anything else I can do before an RMA as shipping back to the US will be an issue for my company. How did you get your issue resolved in the end? Via RMA or did you find a solution?

                    Hoping to hear from you.

                    Kind regards,
                    Joshua Rebello.

                    A 1 Reply Last reply Reply Quote 0
                    • A
                      Andre Moura @JoshRebello
                      last edited by

                      @JoshRebello We solved this issue with an RMA, motherboard was damaged according to the RMA report.

                      J 1 Reply Last reply Reply Quote 0
                      • J
                        JoshRebello @Andre Moura
                        last edited by

                        @Andre-Moura Hi Andre,
                        Thanks for the quick response on this, really appreciate it!

                        Seems like it's mostly going to be an RMA for me as well, letting the company know is going to be tough.
                        By any chance, do you remember the costs your entire RMA process came to? Shipping and back, just trying to get as much info as I can to submit to my company.

                        Thanks in advance!

                        Kind regards,
                        Joshua Rebello.

                        A 1 Reply Last reply Reply Quote 0
                        • A
                          Andre Moura @JoshRebello
                          last edited by

                          @JoshRebello I'm sorry, I don't remember the value.

                          J 1 Reply Last reply Reply Quote 0
                          • J
                            JoshRebello @Andre Moura
                            last edited by

                            @Andre-Moura That's alright, thank you so much for all your help on this!

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