Welcome new user! You can search existing questions and answers without registering, but please register to post new questions and receive answers. Note that due to large amounts of spam attempts, your first three posts will be manually moderated, so please be patient.
Because of un-manageable amounts of spam despite our use of CAPTCHAs, email authorization, and other tools, we have discontinued this forum (see the 700k+ registered users with validated email addresses at right?). Please email us any questions or post bug reports and feature requests on GitHub at https://github.com/jevois -- The content below remains available for future reference.
Welcome to JeVois Tech Zone, where you can ask questions and receive answers from other members of the community.

Jevois doesn't work after Raspberry PI reboots

0 votes

I've come back to my Jevois after not looking at it for a year or so. I'm resurrecting an old project that I had almost working, but starting with a fresh install of everything. Raspberry Pi 3B powering the Jevois with the two headed USB cable.

I have a python program that runs Jevois and communicates by reading and writing via serial. I have it set up as a daemon to run on startup. When I run it by manually starting it, it runs fine. When I let it run automatically after a reboot, it does not work. I have a log file and I can see that it's not getting any response from the Jevois when run this way. I've tried increasing the wait time before the script fires up and that doesn't seem to help.  When I run it via a manual restart after rebooting, it also doesn't work. It only works if I unplug the Jevois and plug it back in, and then start the daemon.

If I stop the daemon, guvcview runs fine. I do get some errors that might not be useful:

GUVCVIEW: capture_cond wait timedout (5 sec)
V4L2_CORE: Could not grab image (select timeout): Resource temporarily unavailable

Even after I run guvcview, the daemon doesn't work without a restart of the jevois. 

Any ideas?

asked Feb 16, 2020 in User questions by PeterQuinn (1,020 points)

1 Answer

0 votes
Looks like jevois is getting confused somehow. Maybe you have some program like modemmanager (which is on Ubuntu) running on your Pi, which sends some modem probes over the USB-to-Serial port of JeVois on boot?

Looks like ModemManager is available on RPi, maybe you have it installed? Can you try sudo apt purge modemmanager and/or inspect your dmesg logs to see whether there is anything about modem, or ttyACM0 or such?
answered Feb 17, 2020 by JeVois (46,580 points)
Here's the section from dmesg when I boot with the cam attached:


[    5.410167] uvcvideo: Found UVC 1.00 device JeVois-A33 Smart Camera (1d6b:0102)
[    5.429908] uvcvideo 1-1.5:1.0: Entity type for entity Processing 2 was not initialized!
[    5.429928] uvcvideo 1-1.5:1.0: Entity type for entity Camera 1 was not initialized!
[    5.430315] input: JeVois-A33 Smart Camera: JeVois as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.5/1-1.5:1.0/input/input0
[    5.430540] usbcore: registered new interface driver uvcvideo
[    5.430548] USB Video Class driver (1.1.1)
[    5.433194] cdc_acm 1-1.5:1.2: ttyACM0: USB ACM device
[    5.433918] usbcore: registered new interface driver cdc_acm
[    5.433929] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
[    5.433936] usbcore: registered new interface driver uas
[    5.490559] brcmfmac: F1 signature read @0x18000000=0x1541a9a6
[    5.500467] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43430-sdio for chip BCM43430/1
[    5.500742] usbcore: registered new interface driver brcmfmac
[    5.706673] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43430-sdio for chip BCM43430/1
[    5.706764] brcmfmac: brcmf_c_process_clm_blob: no clm_blob available (err=-2), device may have limited channels available
[    5.708087] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM43430/1 wl0: Oct 23 2017 03:55:53 version 7.45.98.38 (r674442 CY) FWID 01-e58d219f
[    7.938188] random: crng init done
[    7.938219] random: 7 urandom warning(s) missed due to ratelimiting
[    8.116525] uart-pl011 3f201000.serial: no DMA platform data
[    8.166283] 8021q: 802.1Q VLAN Support v1.8

Here's the section from dmesg when I unplug and plug in the cam after it has already booted:
[  411.093126] usb 1-1.5: USB disconnect, device number 4
[  422.651408] usb 1-1.5: new high-speed USB device number 5 using dwc_otg
[  422.782173] usb 1-1.5: New USB device found, idVendor=1d6b, idProduct=0102, bcdDevice= 1.00
[  422.782186] usb 1-1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[  422.782196] usb 1-1.5: Product: JeVois-A33 Smart Camera
[  422.782205] usb 1-1.5: Manufacturer: JeVois Inc
[  422.783536] uvcvideo: Found UVC 1.00 device JeVois-A33 Smart Camera (1d6b:0102)
[  422.785935] uvcvideo 1-1.5:1.0: Entity type for entity Processing 2 was not initialized!
[  422.785954] uvcvideo 1-1.5:1.0: Entity type for entity Camera 1 was not initialized!
[  422.786415] input: JeVois-A33 Smart Camera: JeVois as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.5/1-1.5:1.0/input/input1
[  422.789781] cdc_acm 1-1.5:1.2: ttyACM0: USB ACM device
[  422.791070] usb-storage 1-1.5:1.4: USB Mass Storage device detected
[  422.793618] scsi host0: usb-storage 1-1.5:1.4
[  423.832108] scsi 0:0:0:0: Direct-Access     JeVois   Smart Camera     0333 PQ: 0 ANSI: 2
[  423.833060] sd 0:0:0:0: Power-on or device reset occurred
[  423.836867] sd 0:0:0:0: [sda] Attached SCSI removable disk
[  423.840688] sd 0:0:0:0: Attached scsi generic sg0 type 0

I don't see anything amiss here.

Modemmanager wasn't installed.
...