VOXL2 Board: Unable to Connect to ADB Shell, DS2 LED Issue

[Dhatchayani L]

I'm experiencing an issue with my VOXL2 board where it fails to connect to adb shell. Normally, when the board powers on, the three LEDs (D1, DS2, and D3) light up, and after 5 seconds, the DS2 LED turns off, allowing the adb shell connection to establish. However, now the DS2 LED remains lit, preventing any communication through USB, Ethernet, or SSH. The board also does not appear in lsusb.

When I force the board into fastboot mode using SW1, I can see the device listed with the fastboot devices command and in lsusb. Similarly, in QDL mode, the device is detectable with the appropriate indications. However, until the DS2 LED turns off, the board remains unresponsive to all other communication methods. This is also preventing me from attempting the unbricking process.

Here, I’ve attached images of the VOXL2 board connectivity and the terminal outputs for lsusb and adb devices. Could you provide guidance on how to resolve this issue?

[Gary Holmgren]

@Dhatchayani-L Having this same issue unfortunately. I thought my voxl2 was bricked. I followed the unbrick procedure tried many different cables, and provision ufs keeps failing in the web portal.

[tom]

@Dhatchayani-L Can you run sudo dmesg -wH in a terminal, unplug all peripherals from your VOXL 2, and then plug in USB and power and seeing what dmesg says during enumeration?

[Gary Holmgren]

@Gary-Holmgren Turns out it wasn’t bricked my previous SDK had failed due to a connection issue in the cable and I just needed to reflash normally.

[tom]

@Gary-Holmgren Thanks for the update!