@stevedan @bensusana I'm also facing this issue. Have you been able to solve this?

@Alex-Kushleyev Where could we find the documentation for this?

Should we build it with the firmware?

@lccarter From where do you set the Baud Rate for FC firmware?

Can Doodle Labs Helix [add-on kit] provided by ModalAI be integrated with VOXL2 present in Starling drone?

@Eric-Katzfey @tom @Chad-Sweet

@tom Are'nt there any other debugging methods we could try out?

@tom My host machine is using Ubuntu 20.04. Based on documentation provided here, I have tried this method a couple of times.

@tom @Eric-Katzfey @modaltb Could you look into?

Voxl 2 is bricked and not responding to adb shell or wifi.
We tried forcing it into fastboot but we couldn't see change.
Tried the qdl method for unbricking by following the guide and got the following response on terminal
"""
<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>
""""
This was the expected output shown on the page as well.
When we switch sw2 switch off though, adb shell still isnt loading
When the sw2 switch is on voxl 2 is recognised over usb in lsusb command but when it is off it isnt being recognised over lsusb either