Posts made by Kashish Garg 0

@tom You mean is it going to EDL mode after replacing power/usb and moving the EDL Switch to off?

Bus 005 Device 011: ID 05c6:900e Qualcomm, Inc. USB2.0 Hub

Is what is being printed with lsusb now

@tom I just re ran it and it took around 7 minutes or so and gave the appropriate output:

FIREHOSE READ: <?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="INFO: Calling handler for setbootablestoragedrive" /></data>
FIREHOSE READ: <?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="INFO: Using scheme of value= 1" /></data>
FIREHOSE READ: <?xml version="1.0" encoding="UTF-8" ?>
<data>
<response value="ACK" rawmode="false" /></data>
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>
FIREHOSE READ: <?xml version="1.0" encoding="UTF-8" ?>
<data>
<response value="ACK" rawmode="false" /></data>

@tom Yes the EDL Switch is turned OFF, pointing away from the Processor

@tom

Bus 005 Device 008: ID 05c6:900e Qualcomm, Inc.

Thanks for your help!

@Alex-Kushleyev Hey Alex, we have gone through this procedure a few times, even had a partner to make sure the button was being pressed appropriately. When running fastboot devices, no device gets identified.

@Alex-Kushleyev it was working and we accidentally removed glibc in an attempt to upgrade it. Meaning we couldn't access the shell anymore.

@Alex-Kushleyev I was able to turn off SW2, but I was unable to log into the board using adb. I tried reinstalling adb on my machine, I tried multiple machines and multiple usb-c cables. We have another, working, starling and we are able to log into adb there, so we are pretty sure it has to do with this voxl2 specifically.

@Alex-Kushleyev Thanks for the quick reply!
Went through the unbricking process three times, the output from the qdl command matched exactly what was in the unbricking guide and there were zero indications of any errors throughout the process

Followed instructions from here: https://docs.modalai.com/voxl2-unbricking/ , flashing VOXL 2 QDL Image 14.1a_1.1.2
We cannot connect to the shell of the voxl2 through adb nor fastboot and have gone through the instruction set multiple times.

We noticed on the other working starling we have the system image version is 1.6.2-M0054-14.1a-perf
Any and all help is appreciated to getting this board unbricked.

Hello, because voxl-mpa-to-ros does not output any information on camera_info topic, we were curious if there was a file somewhere on board that could provide the intrinsic calibration information of the TOF Sensor on board?

We were curious if anyone (either as users or from the ModalAI team) has been able to ascertain the propeller coefficients (thrust vs rpm / rpm vs throttle) for the props that come with the Starling V2? We are looking for coefficients specifically to be used for SO3 Control

We are running qvio on the Starling 2 Platform (through voxl_map_to_ros.launch) and had a quick question:

When visualizing the qvio/pose topics in rviz, we can see the pitch and yaw is inverted. I decided to look at the raw Unix pipe data for qvio (through voxl-inspect-qvio) and it seems to be identical to the messages being published on that rostopic. My theory is that, because the body frame of the Starling 2 has its Z-axis pointing downward and ROS assumes its Z axis to point upward, we are seeing this behavior.

Our idea is to just modify our state estimation node to transform the pose data from qvio by adjusting the roll by 180 degrees. Before doing so, I wanted to check if there is any existing infrastructure to aid with this?
Inverted Pose Video