Hi, there’s a forum thread about this that another user had to deal with the same issue. You have to disable the security setting on Mac that disables programs from having access to HID devices.
The situation did not change after granting OpenMV permission to access the USB HID…
I have also now terminated the virus security software in the attached image.
Thank you for your reply.
I tried to find OpenMV.app at System Preferences > Security & Privacy > Privacy > Accessibility
But I couldn’t.
Am I doing something wrong?
Postscript:
During the installation of another application, a different Accessibility screen opened and I was able to add OpenMV.app.
After doing this, I opened OpenMV with sudo from Terminal, but the result was still the same.
Sure! @axx_kawamura You have to enable Input Monitoring [System Preferences > Security&Privacy > Input Monitoring]. Since it is classified as a HID-Device, it could be an external keyboard, so the system thinks the IDE is trying to read its input (keystrokes).
Sure! But it looks like @axx_kawamura did exactly what I did with enabling the Input Monitoring. The only difference I see is that I didn’t test it in DFU mode. I simply enable the Input Monitoring, restart the OpenMV IDE and connect the board without jumping the SBL pin.
(my OS is in German, so I will ad the name to the pictures)
Mmm, delete that ~/.config/OpenMV folder. That’s happening because all its files are probably marked as root-owned. So, when launched in user mode, it cannot do anything anymore to control its settings. When you launch the IDE in root mode this can happen as it will then write files as if it were the super user… so, then when launched it user mode it cannot edit the same files again it wrote.
Regarding the update issue, I’m not sure what to do… I don’t have a Mac and the @sim showed the fix that works. I found that fix after searching why Macs block HID access.
Do you have access to another non-Mac computer you can run the IDE from? All our other camera modules don’t use HID mode to update the firmware, so, they don’t have this issue. However, the bootloader for the RT1062 is from NXP who wanted to use HID USB mode instead of DFU (which is meant for this) for some reason.