Hello,
I trained an Edge Impulse model and have tried to deploy it to my OpenMV M7 camera. I am trying to use the recommended firmware method but I have run into an issue. When I go to upload the firmware for the M7 camera that I downloaded, I get the following error
No matching interface for the selected file name!
VID: 14277, PID: 37379
I have run lsusb
on my machine and got the following output in case it may help
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 001 Device 003: ID 5986:211b Bison Electronics Inc. HD Webcam
Bus 001 Device 004: ID 8087:0026 Intel Corp. AX201 Bluetooth
Bus 001 Device 022: ID 37c5:1203 OpenMV OpenMV Virtual Comm Port in FS Mode
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Thank you!
Hi, are you trying to load the tflite file using Run Bootloader? That’s for loading a firmware.bin file. Typically, you copy the .tflite file to the OpenMV Cam disk.
Hello, no I am trying to use the .bin file for the M7 camera specifically the one titled edge_impulse_firmware_openmv_cam_m7.bin
. There is no tflite file included in the zip, just a bunch of firmware bin files and the python script.
Rename the file, firmware.bin
. The IDE uses the file name to determine which DFU bootloader interface to use.
That said, we’re about to release a new IDE in a few days which has support for ROM FS which will remove the need to flash a firmware.bin from edge impulse and you’ll be able to load the model directly through flash through the IDE.
1 Like
Awesome that did fix the issue! The only problem I have now is when with the firmware installed I have the error ImportError: no module named 'ml.utils'
when I try to run the included Python script
Hmm…
So, that would imply the firmware and examples they are providing are out of sync. Can you post the files?
I am unfortunately unable to attach files as I am too new of a user.
You should be able to attach files now.
Thank you! Please see the attached files as requested. This is the exact zip file I had downloaded from my Edge Impulse model.
maze-letter-open-mv-fw-v4.zip (8.3 MB)
I don’t know what’s wrong with this firmware. When I load it the board goes into an infinite crash loop.
Our new IDE which features ROMFS resolves this issue with them needing to generate custom firmware. It’s almost ready. Please download the windows dev release from here:
openmv-ide-windows-4.6.1.exe
Then, on connect to the camera, click the firmware version button in the status bar to update the firmware. After doing so, you can go to the Edit ROMFS menu under Tools->ROMFS and just load the tensorflow library into the ROMFS partition.
Once you do that it can be loaded using the ML Model() object via a path like “/rom/”
Hello,
It has been a little while but I did try that dev release and it did solve the import issue. However, initially I was getting an error when loading the tflite file where it would report a tensor error. I was just about to post what that error was but I just upgraded OpenMV IDE to the latest version today and now have a new issue.
I wanted to show a screenshot of the files existing in the ROMFS but now my OpenMV cam just gets stuck when doing anything with the ROMFS (saving a new ROMFS image to the camera, editing it, resetting it, etc).
Output of dfu-util
dfu-util 0.10-dev
Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc.
Copyright 2010-2021 Tormod Volden and Stefan Schmidt
This program is Free Software and has ABSOLUTELY NO WARRANTY
Please report bugs to http://sourceforge.net/p/dfu-util/tickets/
Waiting for device, exit with ctrl-C
dfu-util: Warning: Invalid DFU suffix signature
dfu-util: A valid DFU suffix will be required in a future dfu-util release
Hi, which OS are you on? I see you mentioned lsusb, so, linux?
Did you let the IDE install the udev rules? If not, then the OpenMV DFU bootloader will not be attached. Please check that our udev rules have been installed under /etc/udev/rules.d/
Also, was the OpenMV Cam DFU bootloader updated to the latest? The IDE forces you to reflash the firmware and bootloader when updating to v4.7.0. Did you do this? It should have prompted an update for anything related to ROMFS.