Post-Crash Sentinel Wi-Fi modem issue

[Jgaucin]

Hello,

Crashed the sentinel last week, there don't appear to be any serious damages, just a landing/docking part, the propellors, and one motor.

So, when I went to turn it on to inspect the VOXL-2 chipset, the Wi-Fi modem wasn't lighting up blue and I couldn't see the Wi-Fi acting as a SoftAP so that I could connect via ssh. I assumed it was a problem with the power but it was getting power from the battery as I could hear it, and there don't appear to be any frays or anything loose with the wires. Therefore, I connected via USB to establish an ADB connection, however I encountered an error, or a discrepancy, when I saw the listing for the usb device I connected to. The discrepancy didn't allow me to connect through adb shell as it wasn't being read in adb devices in Ubuntu.

Qualcomm CDMA Technologies MSM QUSB_BULK_CID:0412_SN:7C367221

That was the name of the USB device, whereas previously it was listed something along the lines of Qualcomm KONA_ [...] which was when it worked perfectly.

In addition, in Ubuntu when I ran lsusb, it mentioned something about the Wi-Fi modem being in QBI(?) mode, I apologize I will give more specifics soon.

I can give more specific details later on, as I am not with the Sentinel currently, but any tips on troubleshooting this issue, or figuring out what was happening with the Wi-Fi modem would be greatly appreciated, thank you.

[Jgaucin]

@Jgaucin

Ok so I am with the Sentinel now, here's what it lists out on a windows terminal when I run: Get-PnpDevice -PresentOnly | Where-Object { $_.InstanceId -match '^USB' }

Status Class FriendlyName InstanceId
Error QUSB_BULK_CID:0412_SN:7C367221 USB/VID_...

In addition, when I run it on Ubuntu and run lsusb here's the message I got for the Qualcomm USB:

Bus 001 Device 012: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)

This is the QDL mode I mentioned that I don't quite know what it means. ADB still can't read this device when I run adb devices either.

Also, when I try to bind my Spektrum - SPMR6655 remote to the drone, it shows DSMX on the top left of the screen, which indicated a connection, however there is no flash of orange or blinking or sustained light from the receiver on the drone. I'm believing it to be a power issue now, but I am not sure.

Thanks!

[tom]

@Jgaucin I would take a look here to see if following the unbricking process solves your issue: https://docs.modalai.com/voxl2-qdl/

[Jgaucin]

@tom When trying to initiate the flash (turning the SW2 switch to ON mode), I ran the command prompted. However, it gave me an error and didn't take 10-15 minutes to flash, and almost immediately gave me the error not sure why. I am currently running Ubuntu on Mac through Parallels

Here's the code I ran (not sure what's relevant you can skip to the end for the error):

parallels@ubuntu-linux-22-04-desktop:~/Desktop/Parallels Shared Folders/iCloud/1.1.2-M0054-14.1a-FLAT-V3/ufs$ sudo qdl --debug --storage ufs --include . prog_firehose_ddr.elf rawprogram_unsparse0.xml rawprogram1.xml rawprogram2.xml rawprogram3.xml rawprogram4.xml rawprogram5.xml patch0.xml patch1.xml patch2.xml patch3.xml patch4.xml patch5.xml
[sudo] password for parallels:
HELLO version: 0x2 compatible: 0x1 max_len: 1024 mode: 0
READ64 image: 13 offset: 0x0 length: 0x40
(...)
READ64 image: 13 offset: 0xaa278 length: 0x1000
END OF IMAGE image: 13 status: 0
DONE status: 1
FIREHOSE READ: <?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="INFO: Binary build date: Aug 17 2021 @ 23:37:37" /></data>
LOG: INFO: Binary build date: Aug 17 2021 @ 23:37:37
FIREHOSE READ: <?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="INFO: Binary build date: Aug 17 2021 @ 23:37:37
" /></data>
LOG: INFO: Binary build date: Aug 17 2021 @ 23:37:37
FIREHOSE READ: <?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="INFO: Chip serial num: 2083942945 (0x7c367221)" /></data>
LOG: INFO: Chip serial num: 2083942945 (0x7c367221)
FIREHOSE READ: <?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="INFO: Supported Functions (15):" /></data>
LOG: INFO: Supported Functions (15):
FIREHOSE READ: <?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="INFO: program" /></data>
LOG: INFO: program
FIREHOSE READ: <?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="INFO: read" /></data>
LOG: INFO: read
FIREHOSE READ: <?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="INFO: nop" /></data>
LOG: INFO: nop
FIREHOSE READ: <?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="INFO: patch" /></data>
LOG: INFO: patch
FIREHOSE READ: <?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="INFO: configure" /></data>
LOG: INFO: configure
FIREHOSE READ: <?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="INFO: setbootablestoragedrive" /></data>
LOG: INFO: setbootablestoragedrive
FIREHOSE READ: <?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="INFO: erase" /></data>
LOG: INFO: erase
FIREHOSE READ: <?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="INFO: power" /></data>
LOG: INFO: power
FIREHOSE READ: <?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="INFO: firmwarewrite" /></data>
LOG: INFO: firmwarewrite
FIREHOSE READ: <?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="INFO: getstorageinfo" /></data>
LOG: INFO: getstorageinfo
FIREHOSE READ: <?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="INFO: benchmark" /></data>
LOG: INFO: benchmark
FIREHOSE READ: <?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="INFO: emmc" /></data>
LOG: INFO: emmc
FIREHOSE READ: <?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="INFO: ufs" /></data>
LOG: INFO: ufs
FIREHOSE READ: <?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="INFO: fixgpt" /></data>
LOG: INFO: fixgpt
FIREHOSE READ: <?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="INFO: getsha256digest" /></data>
LOG: INFO: getsha256digest
FIREHOSE READ: <?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="INFO: End of supported functions 15" /></data>
LOG: INFO: End of supported functions 15
qdl: firehose operation timed out
FIREHOSE WRITE: <?xml version="1.0"?>
<data><configure MemoryName="ufs" MaxPayloadSizeToTargetInBytes="1048576" verbose="0" ZLPAwareHost="1" SkipStorageInit="0"/></data>

FIREHOSE READ: <?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="INFO: Calling handler for configure" /></data>
LOG: INFO: Calling handler for configure
FIREHOSE READ: <?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="INFO: Storage type set to value UFS" /></data>
LOG: INFO: Storage type set to value UFS
FIREHOSE READ: <?xml version="1.0" encoding="UTF-8" ?>
<data>
<response value="ACK" MemoryName="UFS" MinVersionSupported="1" Version="1" MaxPayloadSizeToTargetInBytes="1048576" MaxPayloadSizeToTargetInBytesSupported="1048576" MaxXMLSizeInBytes="4096" DateTime="Aug 17 2021 - 23:37:37" /></data>
[CONFIGURE] max payload size: 1048576
FIREHOSE WRITE: <?xml version="1.0"?>
<data><program SECTOR_SIZE_IN_BYTES="4096" num_partition_sectors="32776" physical_partition_number="0" start_sector="3154440" filename="qti-ubuntu-robotics-image-qrb5165-rb5-sysfs_1.ext4"/></data>

FIREHOSE READ: <?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="INFO: Calling handler for program" /></data>
LOG: INFO: Calling handler for program
FIREHOSE READ: <?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="ERROR: Failed to initialize (open whole lun) UFS Device slot 0 partition 0" /></data>
LOG: ERROR: Failed to initialize (open whole lun) UFS Device slot 0 partition 0
FIREHOSE READ: <?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="ERROR: Failed to open the device:3 slot:0 partition:0 error:0" /></data>
LOG: ERROR: Failed to open the device:3 slot:0 partition:0 error:0
FIREHOSE READ: <?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="ERROR: OPEN handle NULL and no error, weird 344489460" /></data>
LOG: ERROR: OPEN handle NULL and no error, weird 344489460
FIREHOSE READ: <?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="ERROR: Failed to open device, type:UFS, slot:0, lun:0 error:3" /></data>
LOG: ERROR: Failed to open device, type:UFS, slot:0, lun:0 error:3
FIREHOSE READ: <?xml version="1.0" encoding="UTF-8" ?>
<data>
<response value="NAK" rawmode="false" /></data>
[PROGRAM] failed to setup programming
parallels@ubuntu-linux-22-04-desktop:~/Desktop/Parallels Shared Folders/iCloud/1.1.2-M0054-14.1a-FLAT-V3/ufs$

Should I continue with the tutorial/guide or stop and figure out this one error?

Thanks!

[tom]

@Jgaucin When you switch the board into EDL mode with SW2 and boot, what mode does the board enumerate in? (with lsusb)

[Jgaucin]

@tom said in Post-Crash Sentinel Wi-Fi modem issue:

When you switch the board into EDL mode with SW2 and boot, what mode does the board enumerate in? (with lsusb)

Right after the USB device was listed as:

Bus 001 Device 009: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)

Then after turning it off and on it stayed the same, then I tried switching it off and on and both times, and power-cycling but it stayed the same as above.

Was the flash unsuccessful? If so, how should I proceed? I am quite stumped on this issue and am very new to UAVs and procedures like this, apologies.

Thanks again!

[tom]

@Jgaucin Yeah it doesn't seem as though the flash ever started, it does seem as though your VOXL2 is booting into the correct mode though.

If you try the flash again do you get the same result?

If not, it's possible that the hardware was damaged

[Jgaucin]

@tom
Hello,

I tried flashing again and ran into the same error. There might be some damage to the VOXL-2. I am also running Ubuntu 22.04 ARM on my MacBook Pro through Parallels but I doubt that could be the issue.

Is there a way I can send you images of the USB debug V2 and the VOXL2? (since the ones I link are too large to send in this forum) There could be some glaring error I am not seeing

I ordered another drone since it's probably not able to be unbricked. In the meanwhile, I'll try salvaging some parts, seeing what works, hopefully the VOXL2 isn't completely unsalvagable, I'm not sure what else to try on this.

Thanks for all your help.

[tom]

@Jgaucin You can check out https://www.modalai.com/pages/rma and we can attempt to recover your board