firmware: 5.0.0 custom build, both HP and HE uploaded
I am using a script to collect IMU and image data to raspberry pi (usb connected) for a hour (I have done this before). After maybe half hour, I notice device disconnected. After I unplug & plug in usb cable, the LED did not blink at all and device not show up. touch fron “openmv” logo feel warmer than usual but no strange smell. After let AE3 cooled down a while, plug it back and LED blink green as usual, device show up in host. But only last for less than 1 minute and it disappear. Try to use IDE to reflash firmware but failed to upload firmware. I guess maybe DC-DC converter is malfunction? Thank you
Hmm, not quite sure. We’ve had no reports ever of it overheating.
Can you remove the case and take some high res pics of the front and back?
Can you remove the case
How to remove the case properly (without break it) ? Thank you
Use a flat head screw driver to pop off the tabs on the front of the case and then it should open up.
Looks fine. Okay, do you see that little switch in the board? Move it to on. Then plug into the PC, click connect after a few seconds, follow the prompts, and OpenMV ide will reflash from scratch. It can reset the bootloader and all firmware onboard.
Hmmm, seems like hardware damage. Okay, just a question: how were you powering it on the system you were using? Was 5V ever applied to the 3.3V rail or any I/O pins on the camera? Was the USB 5V from a PC?
Also, did you erase the flash file system onboard the camera when resetting it? If you have a script that calls deepsleep or lightsleep saved onboard, it would cause the system to act like this. I don’t think this is your problem in this case, but I want to check.
Thank you for replying
how were you powering it on the system you were using?
USB
did you erase the flash file system onboard the camera when resetting it
Yes. and I do not have any script call deepsleep() or lightsleep(), only machine.idle()
Okay, I’d like to see what’s going on with it if possible. I’ll DM you.