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

    Voxl2 crashed

    Ask your questions right here!
    3
    11
    621
    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.
    • S
      SimonLi
      last edited by

      Hi ModalAI team,

      I'm having a voxl2 crash, I don't know why. I tried to connect voxl 2 using adb and ssh but no response.

      Is there a way to see the system log or other way to find the problem?

      And I find DBG_UART12 at J3 PIN-OUT of voxl2. Can I use it to check if voxl2 is completely crashed or just adb and ssh not working?
      If possible, what is the DBG_UART12's reference voltage and baudrate.

      thanks,
      Simon

      ModeratorM 1 Reply Last reply Reply Quote 0
      • ModeratorM
        Moderator ModalAI Team @SimonLi
        last edited by

        @SimonLi can you please follow the steps here? https://docs.modalai.com/voxl2-unbricking/

        S 1 Reply Last reply Reply Quote 0
        • S
          SimonLi @Moderator
          last edited by

          @Moderator
          The problem I encountered was that ADB and SSH did not respond after booting VOXL2 for a while, but it worked after rebooting.

          Not ADB is unable to detect VOXL2.

          So I want to see the system log or other way to find the problem.

          Thanks,
          Simon

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

            @SimonLi What do you see with lsusb on your host machine with voxl2 connected?

            S 1 Reply Last reply Reply Quote 0
            • S
              SimonLi @tom
              last edited by

              @tom
              Although ADB and SSH are unresponsive, I can see the device in Windows 11's Device Manager.

              Simon

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

                @SimonLi It'll be easier to help with debugging if you're using a linux machine, preferably with Ubuntu 18 or newer.

                What is the device enumerating as? Does it give a specific name / device type? We've seen weirdness with ADB + WSL in the past

                S 1 Reply Last reply Reply Quote 0
                • S
                  SimonLi @tom
                  last edited by SimonLi

                  @tom
                  When ADB and SSH are unresponsive and I also repluged the USB, it also showed the same name.
                  The device name is "KONA-QRD_SN:886DD761" in Windows 11's Device Manager.

                  The situation doesn't always happen when VOXL2 booted.
                  And it happens approximately a few minutes after VOXL2 boots, not immediately after booting.

                  Simon

                  ModeratorM 1 Reply Last reply Reply Quote 0
                  • ModeratorM
                    Moderator ModalAI Team @SimonLi
                    last edited by

                    @SimonLi could there be software running that it is causing it to overheat? Maybe put a fan over it so you can get it booted and debug what is going on?

                    S 1 Reply Last reply Reply Quote 0
                    • S
                      SimonLi @Moderator
                      last edited by SimonLi

                      @Moderator
                      I also suspected whether it was due to overheating, so I used voxl-inspect-cpu to check the CPU status.

                      When ADB and SSH were unresponsive, the temperature was about 50°C~55°C, and voxl-inspect-cpu also didn't respond.

                      But if VOXL2 operated normally, there was no problem if the temperature had reached about 80°C.

                      Simon

                      ModeratorM 1 Reply Last reply Reply Quote 0
                      • ModeratorM
                        Moderator ModalAI Team @SimonLi
                        last edited by

                        @SimonLi Once it hits 90° C it will shut down. So, if you were running at 80° C for an extended period of time, it likely shut down.

                        You should put a fan on it and see if you can get it to boot, then disable all of the software, upgrade to the latest SDK, and see if you can bring things back up

                        S 1 Reply Last reply Reply Quote 0
                        • S
                          SimonLi @Moderator
                          last edited by SimonLi

                          @Moderator
                          Thanks, I will try it.

                          Although the temperature will reach 80°C, there has been no shutdown at this temperature.
                          The temperature wasn't high when the problem occurred.

                          So if the problem occurs and I want to view the system logs or use DBG_UART12 at J3 PIN-OUT of voxl2 to check.
                          What can I do?

                          Simon

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