Cannot communicate over adb/fastboot after flashing image
-
@Kashish-Garg-0 , I understand.
Can you try this procedure to force into fastboot and then perform SDK install?
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)
@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 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
-
@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 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
-
@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> -
@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
-
@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
-
@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 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
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login