Hello, I just recently got my hands on an RT1062 and I was going to update the firmware from 4.5.3 to the latest version but I keep getting the following error on Win11 even after putting a jumper on the 3.3V pin and SBL pin. I even tried the zip version but that doesn’t work either.
Error: UsbHidPeripheral() cannot open USB HID device (vid=0x1fc9, pid=0x0135, sn=).
Attached should be a screenshot of what I see in device manager and the driver. Thank you.
You don’t need to do the SBL trick unless the firmware is broken. When you do the firmware update it would actually appear as another device PID.
I’m guessing this didn’t work so you tried the SBL method afterwards right? This invokes the ROM bootloader which has the PID you showed.
Anyway, the RT1062 bootloader appears as a HID device. Not a DFU device. Can you click on that device you showed and go to the details drop down and give me the device VID and PID? We don’t install a driver for the RT1062 bootloader. So, I’m wondering what that device you clicked on is.
… I just checked the IDE driver installer and it definitely don’t deploy a DFU driver for the RT1062s bootloader PID/VIDs.
These are the 2 lines I see under hardware IDs for the Camera DFU Device:
USB\VID_13D3&PID_56EB&REV_1964&MI_04
USB\VID_13D3&PID_56EB&MI_04
For the driver, I manually updated it to be directly from OpenMV but before it was just a default Microsoft driver (signed by Microsoft but still the same name “Camera DFU Device”)
This is the image for when its reinstalled as the default driver:
But, no new HID devices show up when I’m with the jumper unless they’re being generically named “USB Input Device” or " HID Compliant vendor-defined device"
Since you said, I don’t need to try the SBL trick, when I’m trying to upgrade normally, it says connecting,(root directory of the Rt1062 opens up), connecting takes longer than 5s, so I hit cancel, “Unable to connect to your OpenMV Cam’s normal bootloader!”, then I hit ok, then it says the IDE can still try to repair using the SBL bootloader and thats how I got here using the SBL trick.
Full error that I get for using the steps I just mentioned:
C:/Program Files/OpenMV IDE/share/qtcreator/sdphost/win/sdphost.exe -u 0x1FC9,0x0135 – write-file 0x20001C00 C:\Users\pablo\AppData\Roaming\OpenMV\openmvide\firmware\OPENMV_RT1060\sdphost_flash_loader.bin
Error: UsbHidPeripheral() cannot open USB HID device (vid=0x1fc9, pid=0x0135, sn=).
Edit:
The only device I can see normally is COM port, not sure if any of the other settings on the right are affecting it as well:
Hardware IDs:
USB\VID_1209&PID_ABD1&REV_0100&MI_00
USB\VID_1209&PID_ABD1&MI_00
The Camera DFU device is not our hardware. That shouldn’t have our driver.
The COM port when not updating is the OpenMV Cam.
When you attach the SBL wire to 3.3V a HID USB device in devices will appear with the 0x1fc9, 0x0135 VID/PID.
Anyway, the the IDE will show a USB logo when it finds the VID/PID of the serial bootloader. I’m guessing it sees the device but then fails to open it.
You may need to run the IDE in admin mode for this to work as your windows security settings may block the IDE opening a HID device to prevent programs from doing keyboard monitoring. Typically, this isn’t required, but, could be. On Mac, many of our users have had to turn off Mac’s default security settings for the IDE to make this work.
We used the IMX bootloader for this product which uses HID mode. Newer OpenMV Cams will have DFU bootloaders which shouldn’t have this issue.
I found it in device manger but it was under the name “HID compliant vendor defined device.”
I ran the IDE in admin mode but there isn’t any differences still the same issues.
This is while both in DFU mode and in regular mode without clicking anything else:
In the SBL mode the IDE is finding the device. It then executes a command line sbl loader program from nxp to update the firmware.
It displays the same symbol when the camera is in regular mode. It’s just meant to show the IDE found something.
Hmm… if admin mode doesn’t work then something is blocking HID device access on your PC. I’m not quite sure how to help then as it could be anything. Windows PCs don’t require admin mode to talk to the bootloader when it’s a HID device… I was hoping it was some policy that admin mode could bypass.
Given that the IDE sees the device and tries to launch the sblhost program to update the firmware means it’s just a permissions issue for it now working.
Do you have another windows, mac, or linux PC you could use? Mac might be a bit tricky as it blocks HID access by default until disabled. But, linux should 100% be without issues.
I tried a different computer and it updated. I definitely have to check whats blocking HID access on my computer. I appreciate the help! Thank you.