Voxl stuck in waiting after unbricking

[ashwin-umdlife]

Hi Dev Team/ Community Members,

We have procured a few m500 drones from ModalAI. One of them is having the exact same issue as posted here by one of the users.
We are able to communicate with other devices with adb.
We are using ModalAIs power adapter.

We tried the following but was unsuccessful:

• list item adb kill-server

• list item Using other computers to flash

We can flash other devices with the usb-expansion-fastboot module but not this particular m500 drone.

[modaltb]

Hi @ashwin-umdlife , sorry we crossed threads, see here: https://forum.modalai.com/topic/518/unable-to-unbrick-modalai-voxl-m500

[ashwin-umdlife]

@modaltb said in Voxl stuck in waiting after unbricking:

Hi @ashwin-umdlife , sorry we crossed threads, see here: https://forum.modalai.com/topic/518/unable-to-unbrick-modalai-voxl-m500

@modaltb This post is quite different from https://forum.modalai.com/topic/518/unable-to-unbrick-modalai-voxl-m500.

Here I am able to fastboot and start writing an image but gets stuck at the part were the board reboots and waits for the device. Please see this https://forum.modalai.com/topic/402/voxl-stuck-in-waiting-for-device-after-unbricking post. @Chad-Sweet recommended using adb kill-server and the user tried a different PC to flash. But both these methods didn't work for us.

[ashwin-umdlife]

@modaltb @Chad-Sweet This issue has happened to another drone of ours. Could you please take a look at this ?

[modaltb]

Hi @ashwin-umdlife ,

We might need to setup a screen share if possible, can you let me know what timezone and then I'll try to schedule something.

From what I understand, you have attempted to re-flash the VOXL system image on QTY2 units now and both proceed through the process but are stuck at [INFO] Waiting for device...

In the platform release download folder, can you please go here and try to run this script directly?

cd voxl_platform_3-3-0-0.4.6-b/system-image
sudo ./flash_build_apps.sh

If after this you are still stuck in [INFO] Waiting for device..., can you try:

• run fastboot devices or sudo fastboot devices
• if a device shows up, then run sudo fastboot reboot to bring it out of fastboot (hopefully)

Thanks for your patience.

[modaltb]

Hi @ashwin-umdlife ,

We might need to setup a screen share if possible, can you let me know what timezone and then I'll try to schedule something.

From what I understand, you have attempted to re-flash the VOXL system image on QTY2 units now and both proceed through the process but are stuck at [INFO] Waiting for device...

In the platform release download folder, can you please go here and try to run this script directly?

cd voxl_platform_3-3-0-0.4.6-b/system-image
sudo ./flash_build_apps.sh

If after this you are still stuck in [INFO] Waiting for device..., can you try:

• run fastboot devices or sudo fastboot devices
• if a device shows up, then run sudo fastboot reboot to bring it out of fastboot (hopefully)

Thanks for your patience.

[ashwin-umdlife]

@modaltb Tried all the steps mentioned above. But unfortunately nothing works.

Can we please schedule a meeting? How can I contact you?

[ashwin-umdlife]

This post is deleted!

[ashwin-umdlife]

This post is deleted!

[ashwin-umdlife]

@modaltb I have an email to contact@modalai.com from our company email.

[modaltb]

Invite sent, we can do a screen share and see what's up. thanks!

[wilkinsaf]

Wanted to update this by saying I experienced same issue, but I resolved this by disconnecting tracking camera that had been installed upside down. So, if anyone is reading this in the future....try disconnecting your cameras attached to the board