See viewtopic.php?t=372520 for policy on 3rd party image sensors.
Pivariety really is Arducam's problem to solve - I don't think I even have any of their Pivariety modules left to test with.
IMX462 is supported by Linux kernel drivers and by libcamera, so there really is no need for the Pivariety mess. Indeed their original IMX462 board had the Pivariety microcontroller as a separate PCB to the sensor, and that works very nicely. There's probably an option to add 2 wire links to bypass their MCU on the latest boards, but I'm not going to look into that.
Check the kernel logs for errors - "dmesg", and "cat /sys/kernel/debug/v4l2-async/pending_async_subdevices".
I see nothing in the overlay that should cause grief. Enabling the serial port will lock the VPU core clock at 250MHz, which will also lock the I2C bus at full speed. It's just possible that their microcontroller then can't keep up with the I2C requests.
Pivariety really is Arducam's problem to solve - I don't think I even have any of their Pivariety modules left to test with.
IMX462 is supported by Linux kernel drivers and by libcamera, so there really is no need for the Pivariety mess. Indeed their original IMX462 board had the Pivariety microcontroller as a separate PCB to the sensor, and that works very nicely. There's probably an option to add 2 wire links to bypass their MCU on the latest boards, but I'm not going to look into that.
Check the kernel logs for errors - "dmesg", and "cat /sys/kernel/debug/v4l2-async/pending_async_subdevices".
I see nothing in the overlay that should cause grief. Enabling the serial port will lock the VPU core clock at 250MHz, which will also lock the I2C bus at full speed. It's just possible that their microcontroller then can't keep up with the I2C requests.
Statistics: Posted by 6by9 — Wed Jul 24, 2024 2:43 pm