The uploader that worked for you doesn’t filter by the PID and vid so it didn’t care.
I removed the udev rules, but still no joy. The log in dmesg when I connect my cam is:
[875424.766530] usb 2-1.2.2: new full-speed USB device number 36 using ehci-pci
[875424.877244] usb 2-1.2.2: New USB device found, idVendor=1209, idProduct=abd1
[875424.877254] usb 2-1.2.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[875424.877260] usb 2-1.2.2: Product: OpenMV Virtual Comm Port in FS Mode
[875424.877265] usb 2-1.2.2: Manufacturer: OpenMV
[875424.877269] usb 2-1.2.2: SerialNumber: 000000000011
[875424.877737] cdc_acm 2-1.2.2:1.0: ttyACM0: USB ACM device
[875424.878104] usb-storage 2-1.2.2:1.2: USB Mass Storage device detected
[875424.878335] scsi host35: usb-storage 2-1.2.2:1.2
[875425.876142] scsi 35:0:0:0: Direct-Access uPy microSD Flash 1.00 PQ: 0 ANSI: 2
[875425.876602] sd 35:0:0:0: Attached scsi generic sg2 type 0
[875425.877351] sd 35:0:0:0: [sdc] 97 512-byte logical blocks: (49.6 kB/48.5 KiB)
[875425.877968] sd 35:0:0:0: [sdc] Write Protect is off
[875425.877975] sd 35:0:0:0: [sdc] Mode Sense: 00 00 00 00
[875425.878592] sd 35:0:0:0: [sdc] Asking for cache data failed
[875425.878598] sd 35:0:0:0: [sdc] Assuming drive cache: write through
[875425.888105] sdc: sdc1
[875425.891214] sd 35:0:0:0: [sdc] Attached SCSI removable disk
[875431.746159] FAT-fs (sdc1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
I’ll make a version of the Ide tonight that will print out the info it sees. This will let me know what device type I need to look for.
Does the OpenMV cam appear as a try serial port? In dev?
Yes, it appears as a disk and as a serial on /dev/ttyACM0. I can use screen to have normal python console there.
Please try this version of the IDE out (assumed you had 64-bit linux) http://openmv.io/upload/openmv-ide-linux-x86_64-1.2.0/openmv-ide-linux-x86_64-1.2.0.run.
I don’t have all the fixes I’ve been working on in this version of the IDE. I just disabled the port filtering. Please let me know what you see in the port list. It should print out this:
name=ttyACM0,hasVID=1,hasPID=1,VID=1209,PID=abd1
Thanks, I will try it. By the way, you could add a mime type to your web server configuration (or a content-disposition header), so that it doesn’t serve those files as text, but downloads them instead. Just a small thing.
After clicking “connect” I get a message box with “name=ttyACM0,hasVID=1,hasPID=1,VID=8086,POD=1e26” with this version. Then it prompted me to upgrade the firmware, the to erase the filesystem, then it began programming. Once finished, it asked me to wait for reconnect before continuing. Then it displayed an empty message box with a comic balloon with blue letter “i” in it. Finally, an error message popped up with text “No openmv cams found” and it asked if I have an openmv attached and it’s bricked – just like the previous time. I clicked “cancel”, and clicked on “connect” again. Then it asked me to associate a drive with the camera, showing my EFI partition as the default (the camera was the second option). Then it finished, and I was able to run the hello world example.
Okay,
Um, about the EFI partition. Is that a FAT partition? I’d like to filter that out possibly for you. Right now the IDE looks for FAT partitions that are writable.
As for the PID and VID. That’s odd… Pretty sure it was tje Foss one before.
I think this is one of the first cameras with the new sensor. You sent it to me for testing, after I tested the fire-sale camera a bit. Perhaps it’s somehow different from the kickstarter ones (I haven’t yet unpacked those).
The EFI partition has “EFI System” as the parition type:
/dev/sdb1 2048 999423 997376 487M EFI System
But I think that it actually has a FAT filesystem on it.
Hi,
“@Kermit666 - Inability to connect is a separate issue from the USB packets. When you plug in your OpenMV Cam… does it appear as a device in your device manager? If so, what device does it appear as? There’s no IDE fix I can do to solve any problem related to the Cam not connecting to the PC initially.”
When I plug in the Cam it appears as a removable disk, with 31 KB and 3 files inside.
This works perfectly from the beginning
"Two things can be happening:
- The wrong driver is getting loaded for your OpenMV Cam.
- The Cam’s firmware is bad and you need the bootloader to fix it. If 2 is the case the bootloader should be able to connect to the Cam, but, might have trouble re flashing given the packet issue. You’d get a failed to connect to bootloader error here."
I have the lcd module, what happens on the lcd module when I connect the cam ? on my cam + lcd I have only a white lcd, nothing else !
Thanks
Hi, you have to run the LCD demo script. The cam has to be told to update the LCD. Don’t worry, adding LCD to your code is only 1 line.
Deshipu,
Qt has no easy way using the QStorageInfo Class | Qt Core 5.15.10 class to filter out EFI partitions.
I’ll make another installer for linux with a fix to ignore the drive if EFI is in it’s name. However, I need to focus on other things right now.
Wait, I have a fix. I’ll filter out all drives not mounted in media.
That sounds reasonable. Perhaps it would be good to have a way to bypass the filtering altogether, in case of a really weird system setup – for instance, a button that makes it display all mounted drives, or even lets you just enter a path.
After updating as prompted the board is completely unresponsive. Does not show up in devices. LED no longer lit.
I tried several different USB connectors.
It’s dead Jim.
Hi, you can use DFU mode to recover it. On windows the IDE will walk you through this process without requring external software. On Mac and Linux you need to make sure you have some external libraries installed first.
Anyway, Just click the connect button and follow the IDE prompts.
Links to Mac and Linux stuff:
The IDE will literally ask you on connect if your OpenMV Cam is bricked - follow the prompts from there.
Note, once the system starts scanning for your OpenMV Cam just click the cancel button and the IDE will ask you if you want to use the DFU bootloader, say yes.
It says “DFU firmware update failed”.
Hi, can you give some more info? It really helps.
So, what operating system are you using? Did you connect the cam to the PC before clicking “ok” to run the DFU update? Did you attach a jumper wire between BOOT0 and the 3.3V pin or RST?
On windows, if you plug in the cam when it’s in DFU mode it should appear as a USB device and windows will load up the driver for it and make the USB connection sound. If you hear that then you know the board is ready for DFU updating.