VOXL2 SDK Flash Not Working

[ctitus]

@tom I'm not closely related to the people developing that code, I'm just trying to run it. I believe that there was a change to the modal pipe architecture that the code I need to run relies on. What confuses me is that I had no issues rolling back that far on my other VOXL2's, it just the two we bought more recently seem not to work with the install.sh script.

[tom]

@ctitus I would try forcing the voxl2 into fastboot before flashing and seeing if that resolves the issue.

VOXL 2/VOXL2 Mini System Image

ModalAI technical documentation for VOXL and VOXL 2 Companion Computers for PX4 and ArduPilot Obstacle Avoidance and GPS-denied navigation, assembled in the USA

ModalAI Technical Docs (docs.modalai.com)

[ctitus]

@tom Thanks for the suggestion, but it doesn't seem to work.

[tom]

@ctitus What do you see with lsusb? Wondering if the board is being detected at all

[ctitus]

@tom It shows up correctly for everything. I'm wondering if there's something about by laptop specifically that's causing it not to work? Are there error messages or logs anywhere I can look at?

Fastboot: Bus 004 Device 037: ID 18d1:d00d Google Inc. Xiaomi Mi/Redmi 2 (fastboot)
ADB: Bus 004 Device 038: ID 05c6:901d Qualcomm, Inc. KONA-QRD _SN:9E0034D1

[ctitus]

@ctitus I've been trying more sdk's and it seems like none of them will flash properly, but there's no error or anything thrown, just nothing happens.

[tom]

@ctitus Do those two devices show up in lsusb simultaneously?

Does anything show up with adb devices or fastboot devices?

[ctitus]

@tom No, it's only ever 1 at a time. I was able to get my hands on a new fresh linux machine, and after installing the packages I needed (and using the same files I copy and pasted from my original laptop), I was successfully able to factory reset and roll back the sdk and system image without issue. I'm gonna do a bit of digging but I have a feeling I was just missing some packages and it wasn't alerting me of it on my original laptop.

[tom]

@ctitus Interesting, I would also check to make sure your user on that machine has the required permissions, here's an example of the groups that my user is part of for ref:

[ctitus]

@tom So I did some digging and found where it hangs. Line 391 of voxl2_1.3.1-0.8/system-image/flash-system-image.sh: local output="$( fastboot getvar "partition-size:${partition}" 2>&1 )" specifically executing fastboot getvar "partition-size:modalai_conf". For some reason, my original laptop shows "< waiting for any device >" while the laptop that worked returned "partition-size:modalai_conf: 0x4000000". I double checked that the voxl shows up as fastboot with lsusb on both laptops

[ctitus]

@ctitus Messing aroudn a bit more, sudo fastboot getvar "partition-size:modalai_conf" works

[ctitus]

And running sudo ./install.sh worked and successfully installed the SDK and system image

[tom]

@ctitus Thanks for this info, it is very helpful. What OS are you running on the PC that it isn't working?

[ctitus]

@tom Both are linux ubuntu 22.04 LTS. My current laptop I've been using for a while and likely have some weird issue in my user setup or configuration, the new laptop was dual booted as linux for the first time 2 hours ago and the first thing it did was factory reset the voxl and run install.sh (and install the missing dependencies that install.sh alerted me to) which worked just fine without needing sudo. I'm not sure what I could've done to my laptop to have this issue, but any advice would be greatly appreciated

[tom]

@ctitus I would check the groups that your user is part of that I posted above. Maybe also compare the versions of adb and fastboot between the two machines.

[ctitus]

@tom it looks like the groups are the same between machines (and yours except I'm not in docker), and the versions of adb, fastboot, and all android packages are the same. I was looking online and some people say it may be related to or solved by udev (https://askubuntu.com/questions/705537/no-permissions-fastboot-fastboot-and-adb-not-working) but I'm not sure I have more more time to troubleshoot this, and I didn't touch anything with udev on the working machine. Hopefully I'll be able to circle back to this eventually, but thank's for your help with everything!