@modaltb Yes, we used r14.1a_1.1.2-M0054-14.1a-FLAT-V3.zip
as well.
We will make a try with removing all the hardware connection.
@modaltb Yes, we used r14.1a_1.1.2-M0054-14.1a-FLAT-V3.zip
as well.
We will make a try with removing all the hardware connection.
@Eric-Katzfey We've tried replacing power cable with a spare. Tried fastboot and qdl again, but it doesn't work.
@Eric-Katzfey Thanks. We will try as soon as possible. Are there any more possible solutions that might solve this problem?
We need VOXL 2 to work urgently. Can we get any remote assist? Thanks.
@tom Yes, entering into fastboot mode is possible. We tried re-flashing with voxl2_platform_1.3.1-0.8/system-image/flash-system-image.sh
. But after flashing, it doesn't go after but only waiting for ADB.
Done Flashing
[--------------------------------------------------------](100%)
rebooting...
finished. total time: 0.050s
[INFO] Waiting for ADB
@tom Yes, it reached the point. The result is written on the previous replies.
@tom We've ran factory reset with qdl and this is the output.
After performing qdl, if we run lsusb without turning off the power, it gives us this.
If we cycle power and run lsusb, it is still shown below. It is not recognized as 05c6:901d.
@Adrian-Hidalgo We disconnected ToF and reconnected with the original Hi-Res camera. Also, we've checked the camera connections, but had no issue about it. However, we've disconnected GPS module, as we don't need it. Can this be the reason?
@tom This is the full output of lsusb
.