ModalAI Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login
    1. Home
    2. HLaGrone
    H
    • Profile
    • Following 0
    • Followers 0
    • Topics 1
    • Posts 1
    • Best 0
    • Controversial 0
    • Groups 0

    HLaGrone

    @HLaGrone

    0
    Reputation
    3
    Profile views
    1
    Posts
    0
    Followers
    0
    Following
    Joined Last Online

    HLaGrone Unfollow Follow

    Latest posts made by HLaGrone

    • VOXL 2 Returns to fastboot after power cycle.

      Hello, I am troubleshooting a Starling 2 Max with an M0054-1 VOXL2 board that is currently stuck in fastboot mode.

      Initially the board did not enumerate at all over USB (no adb, fastboot, or lsusb). I followed the unbricking procedure here: https://docs.modalai.com/voxl2-unbricking/#starlin-drones-with-m0054-2m0154-2

      Using VOXL2 QDL Image 14.1a_1.7.8, the flash process hangs at the start and times out. Using VOXL2 QDL Image 14.1a_1.1.2, the flash completes successfully. After flashing 14.1a_1.1.2, I powered the board down and returned SW2 to the normal position.

      After this, the board consistently enumerates as a fastboot device on power-up. I then followed the procedure here using the latest SDK: https://forum.modalai.com/topic/2789/voxl2-stuck-in-fastboot

      The flashing process reaches completion and attempts to reboot, but hangs at the step that prompts a manual power cycle after approximately 60 seconds. After power cycling, the DS1 LED rapidly strobes red, but the startup tune still plays. Disconnecting USB-C returns DS1 to solid green and D1 to solid green. Reconnecting USB-C causes the device to enumerate again in fastboot mode and the cycle repeats. Disconnecting it after powering down and not plugging the device in until after a restart does not fix the issue.

      I have tested multiple known-good USB-C cables. Additionally, the blue LEDs on the bottom of the Starling briefly strobe at power-up, then remain off for the rest of the uptime.

      At this point, is there another recovery path I should try, or are these symptoms consistent with a hardware fault?

      Thank you!

      posted in Ask your questions right here!
      H
      HLaGrone