Cannot communicate over adb/fastboot after flashing image
-
@Alex-Kushleyev it was working and we accidentally removed glibc in an attempt to upgrade it. Meaning we couldn't access the shell anymore.
-
@Kashish-Garg-0 , I understand.
Can you try this procedure to force into fastboot and then perform SDK install?
https://docs.modalai.com/voxl2-voxl2-mini-system-image/#force-voxl-2-into-fastboot
-
@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.
-
@Kashish-Garg-0 , I understand, thanks for clarifying.
My colleague, who has more experience with this, was out of office last week, coming back tomorrow. I will make sure he takes a look at your post, he may have some suggestions. @tom
Alex
-
@Kashish-Garg-0 With your device plugged in to your host pc via usb, what do you see with
lsusbon your host PC? -
-
@Kashish-Garg-0 Okay so the device is booting into EDL mode, which is what is used for QDL flashing. Can you confirm that the EDL switch is turned off?
-
@tom Yes the EDL Switch is turned OFF, pointing away from the Processor
-
@Kashish-Garg-0 And when you went through the QDL process did the QDL flashing complete as expected? Should take around 10 minutes to complete
-
@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> -
@Kashish-Garg-0 And then if you remove and replace both power and usb is it still booting to that same mode?
-
@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 HubIs what is being printed with lsusb now
-
@Kashish-Garg-0 Sounds like we'll have get an RMA going for this one: https://www.modalai.com/pages/rma
-
@Kashish-Garg-0 It's possible your board has a QSM8250 (M0054-2) instead of a QRB5165 (M0054-1), see here for the diffs: https://docs.modalai.com/m0054-versions/#m0054-1-and-m0054-2
If that is the case then you will have to QDL using a different build, which you can download from downloads.modalai.com, look for
M0054-2 Starling QDL Image 1.7.4 2024-02-09-1.7.4-M0054-2.zipunder the "All" category
