What hardware/platform were you working on? Raspberry pi zero 2
Instructions you have followed. (link/manual/etc.) – tried both low light native and pivariety
Problems you were having?
Made X/EGL preview window
[18:05:12.983146675] [19211] INFO Camera camera_manager.cpp:299 libcamera v0.0.4+22-923f5d70
[18:05:13.010199240] [19214] WARN CameraSensorProperties camera_sensor_properties.cpp:243 No static properties available for 'imx327'
[18:05:13.010359655] [19214] WARN CameraSensorProperties camera_sensor_properties.cpp:245 Please consider updating the camera sensor properties database
[18:05:13.032619068] [19214] ERROR IPAProxy ipa_proxy.cpp:149 Configuration file 'imx327.json' not found for IPA module 'raspberrypi'
[18:05:13.032795109] [19214] ERROR IPARPI raspberrypi.cpp:234 Could not create camera helper for imx327
[18:05:13.032860473] [19214] ERROR RPI raspberrypi.cpp:1352 Failed to load a suitable IPA library
[18:05:13.033124899] [19214] ERROR RPI raspberrypi.cpp:1277 Failed to register camera imx327 10-001a: -22
ERROR: *** no cameras available ***
The dmesg log from your hardware?
pi@raspberrypi:~ $ dmesg | grep bcm
[ 0.000000] Kernel command line: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_headphones=0 snd_bcm2835.enable_hdmi=1 snd_bcm2835.enable_hdmi=0 video=HDMI-A-1:1920x1080M@60 smsc95xx.macaddr=B8:27:EB:B5:8F:39 vc_mem.mem_base=0x1ec00000 vc_mem.mem_size=0x20000000 console=ttyS0,115200 console=tty1 root=PARTUUID=72f6b9d8-02 rootfstype=ext4 fsck.repair=yes rootwait quiet splash plymouth.ignore-serial-consoles
[ 0.048701] bcm2835-mbox 3f00b880.mailbox: mailbox enabled
[ 0.127509] bcm2835-dma 3f007000.dma: DMA legacy API manager, dmachans=0x1
[ 2.163799] bcm2835-rng 3f104000.rng: hwrng registered
[ 2.164989] gpiomem-bcm2835 3f200000.gpiomem: Initialised: Registers at 0x3f200000
[ 3.121545] bcm2835_vchiq 3f00b840.mailbox: there is not valid maps for state default
[ 3.141724] bcm2835-wdt bcm2835-wdt: Broadcom BCM2835 watchdog timer
[ 3.142025] bcm2835-power bcm2835-power: Broadcom BCM2835 power domains driver
[ 3.143290] mmc-bcm2835 3f300000.mmcnr: mmc_debug:0 mmc_debug2:0
[ 3.143308] mmc-bcm2835 3f300000.mmcnr: DMA channel allocated
[ 3.219948] mmc0: sdhost-bcm2835 loaded - DMA enabled (>1)
[ 8.034686] bcm2835_vc_sm_cma_probe: Videocore shared memory driver
[ 8.422611] snd_bcm2835: module is from the staging directory, the quality is unknown, you have been warned.
[ 8.518667] bcm2835_mmal_vchiq: module is from the staging directory, the quality is unknown, you have been warned.
[ 8.522201] bcm2835_mmal_vchiq: module is from the staging directory, the quality is unknown, you have been warned.
[ 8.528133] bcm2835_mmal_vchiq: module is from the staging directory, the quality is unknown, you have been warned.
[ 8.587293] bcm2835_isp: module is from the staging directory, the quality is unknown, you have been warned.
[ 8.602741] bcm2835_v4l2: module is from the staging directory, the quality is unknown, you have been warned.
[ 8.629539] bcm2835-isp bcm2835-isp: Device node output[0] registered as /dev/video13
[ 8.630969] bcm2835-isp bcm2835-isp: Device node capture[0] registered as /dev/video14
[ 8.631424] bcm2835-isp bcm2835-isp: Device node capture[1] registered as /dev/video15
[ 8.631767] bcm2835-isp bcm2835-isp: Device node stats[2] registered as /dev/video16
[ 8.631801] bcm2835-isp bcm2835-isp: Register output node 0 with media controller
[ 8.631834] bcm2835-isp bcm2835-isp: Register capture node 1 with media controller
[ 8.631851] bcm2835-isp bcm2835-isp: Register capture node 2 with media controller
[ 8.631867] bcm2835-isp bcm2835-isp: Register capture node 3 with media controller
[ 8.651361] bcm2835-isp bcm2835-isp: Device node output[0] registered as /dev/video20
[ 8.651849] bcm2835-isp bcm2835-isp: Device node capture[0] registered as /dev/video21
[ 8.652207] bcm2835-isp bcm2835-isp: Device node capture[1] registered as /dev/video22
[ 8.652484] bcm2835-isp bcm2835-isp: Device node stats[2] registered as /dev/video23
[ 8.652517] bcm2835-isp bcm2835-isp: Register output node 0 with media controller
[ 8.652537] bcm2835-isp bcm2835-isp: Register capture node 1 with media controller
[ 8.652555] bcm2835-isp bcm2835-isp: Register capture node 2 with media controller
[ 8.652572] bcm2835-isp bcm2835-isp: Register capture node 3 with media controller
[ 8.652747] bcm2835-isp bcm2835-isp: Loaded V4L2 bcm2835-isp
[ 8.734917] bcm2835_codec: module is from the staging directory, the quality is unknown, you have been warned.
[ 8.745586] bcm2835-codec bcm2835-codec: Device registered as /dev/video10
[ 8.745651] bcm2835-codec bcm2835-codec: Loaded V4L2 decode
[ 8.748788] bcm2835-codec bcm2835-codec: Device registered as /dev/video11
[ 8.748849] bcm2835-codec bcm2835-codec: Loaded V4L2 encode
[ 8.753010] bcm2835-codec bcm2835-codec: Device registered as /dev/video12
[ 8.753082] bcm2835-codec bcm2835-codec: Loaded V4L2 isp
[ 8.757895] bcm2835-codec bcm2835-codec: Device registered as /dev/video18
[ 8.757957] bcm2835-codec bcm2835-codec: Loaded V4L2 image_fx
[ 8.772925] bcm2835-codec bcm2835-codec: Device registered as /dev/video31
[ 8.772992] bcm2835-codec bcm2835-codec: Loaded V4L2 encode_image
No, I don’t think so. I’ve apparently missed this in a guide somewhere and I’ve had trouble determining which guide I should use for this device. Which one should I use? I’ve tried varying things in /boot/config.txt but definitely nothing with clock-frequency timing and definitely not imx290.
Note, I’m also trying to troubleshoot an Arducam 16MP autofocus but spam bot caught my post.
Hello,
Our automated spam filter, Akismet, has temporarily hidden your post in IMX519 PDAF Release for review.
A staff member will review your post soon, and it should appear shortly.
I’ve been mostly following this guide which does not mention the imx190/327 relationship. Also, I note that I do NOT have an adapter board which is mentioned in the guide. Did not come with one:
But, someone pointed me to your quick start for native cameras and I do now see the chart you refer to here from the standard rpi native libcamera setup.
I’ll now try dtoverlay=imx290, clock-frequency=37125000 in my config.txt and report back
Ok, thanks @edward. I’ve got your newer starvis with the wide angle lens on order.
Also, I’m trying to get an Arducam 16mp autofocus going in another thread… question submitted but trapped by you spam bot and awaiting sysadmin review. Can you free it?
Yes, I do have an rpi4 and other cables. I’ll try cables but unfortunately my application requires very small size enclosure so trying to get this to work on rpiz2.
What would cause the above part of the error in libcamera-hello? Looks like v4l2? I assume this has to do with camera control/io some am wondering if it thinks i have one of the cameras with the ir cut motor or some io peripheral?
Also, at one point in my troubleshooting, I did run rpi-update. I now know you ship drivers for the current kernel distro so am wondering if this caused some of my problems. I tried to rollback but have not tried to reflash as I’ve got some other things setup on the pi I’d have to redo.
Ok. Makes sense. I do recall the loop through pad connecting base of camera to backside of PCB looked loose at one point. I thought I pushed it back into place. Let me investigate but it will be Monday or Tuesday next week.
On this, I’m realizing this was on my autofocus camera, not on my low light. So, disregard. PCB and connections look solid and nothing apparent from eye via magnfying lens.
I’m still stuck on the V4L2 error. Have tried:
Another cable with my rpiz2 – same error
getting it to work with my rpi4. I’m afraid I’ve got trouble with my rpi4 as I’ve got it setup in a headless mode and am not able to easily test this.
I’ve got this camera on order and which is now in the US – should arrive in next few days.
2MP IMX462 Color Ultra Low Light STARVIS Camera Module with 141°(H) Wide-Angle M12 Lens for Raspberry Pi
SKU: B0444
You’ve also helped me troubleshoot my arducam 16mp autofocus so I now have a camera working.
Should I:
Try something else with my rpiz2 and starvis/imx327 camera?
[ 0.057128] platform 3f801000.csi: Fixed dependency cycle(s) with /soc/i2c0mux/i2c@1/imx519@1a
[ 11.501575] imx519 10-001a: Device found is imx519
[ 11.501879] imx519 10-001a: Consider updating driver imx519 to match on endpoints
Maybe you can use your sd card on pi2 to use on pi4, make sure the network configuration is good, you can use the tool to scan ,like advanced_ip_scanner
OK – works great on my rpi4 with no changes to SD card other than config.txt. have also tried several ribbon cables with the rpiz2 just ordered from uctronics.