OpenMV does not upgrade's camera firmware

[dam]

uArm Serial No.: UARM-05051704C5

Firmware Version: latest, just upgraded

Operation System: MacOS Sierra 10.12.5

uArm Controlling Method: uArm Studio 1.1.13-c2

OpenMV IDE 1.6.0

Hi.

When I connect the cam provided with the uArm Pro and follow the connection instructions, when I try step 2, to upgrade the firmware version, a window appears saying that it’s connecting, but it never finishes. OpenMv says the firmware is out of date and should be updated.

If I try to run the “tracking.py” software on OpenMV, the program runs, but I can see no images

What can I do?

Thanks in advance.

DAM

---

UFACTORY Website
Official Store
uArm User Facebook Group

Feedback:
English Channel
中文通道

[tony]

Please have a check here, you may find the answer.

OpenMV tracking.py problems

Hello, I’m using the latest tracking.py and it seems to be confirming the problem I was having with the first version. I’ve connected everything up - OpenMV RX3 to Uarm TX2, OpenMV TX3 to Uarm RX2, I’ve copied it over as main.py, but the OpenMV green light turns on and it never turns off, so it must be failing to even communicate with the Uarm (Swift Pro) over UART. When I add a facial recognition block in Uarm Creator Studio I get a blank white screen. Also, if OpenMV VIN is connected to Uar…

[dam]

Hi. This other topic seems a bit more advanced. I can’t even update the firmware…

[tony]

If you can’t upload the code to openmv, it’s mainly caused by the firmware of openmv (ver.2.4.1). So please reflash the firmware and then try to upload the firmware again. It should work. THANKS

[dam]

Hi. Can you tell me where to find the instructions to perform this.

Thank you.

[dam]

BTW, I use: uArm Pro

uArm Serial No.: UARM-05051704C5

Firmware Version: 3.1.16

Operation System: MacOS Sierra 10.12.6 (recently updated)

uArm Controlling Method: uArm Studio 1.1.13-p2

[tony]

Actually we have already reported the issue to openmv. And they would fix this problem in next release. If you are not in a hurry, please be patient. Or you could reflash the firmware like the picture below, then follow the step 4 in instructions again.