02-13-2021, 08:46 PM
(This post was last modified: 02-13-2021, 08:57 PM by FrancisTheodoreCat.)
I now get the following errors printed to the syslog when I try to access the camera via /dev/video0:
This happens regardless of kernel version, and even when using the trunk build image from the wiki, which I presume works on other PineCubes. Is this a hardware issue, or a kernel/device-tree regression? From my searches on that particular ov5640 error, it's usually a device-tree misconfiguration causing it.
I did check continuity from connector to connector for the CSI cable, and it passed. So if it were a hardware issue, it's likely the camera module itself, which I don't have a spare of to test with.
If anyone else with a working PineCube and a working copy of Armbian is willing to test, I put together a script for using the H3's Cedar H264 acceleration to serve up an HLS stream page:
https://github.com/francistheodorecatte/...mer_hls.sh
Quote:[ 125.371915] i2c i2c-1: mv64xxx_i2c_fsm: Ctlr Error -- state: 0x2, status: 0x0, addr: 0x3c, flags: 0x0
[ 125.381245] ov5640 1-003c: ov5640_read_reg: error: reg=300a
[ 125.386847] ov5640 1-003c: ov5640_set_power_on: failed to read chip identifier
This happens regardless of kernel version, and even when using the trunk build image from the wiki, which I presume works on other PineCubes. Is this a hardware issue, or a kernel/device-tree regression? From my searches on that particular ov5640 error, it's usually a device-tree misconfiguration causing it.
I did check continuity from connector to connector for the CSI cable, and it passed. So if it were a hardware issue, it's likely the camera module itself, which I don't have a spare of to test with.
If anyone else with a working PineCube and a working copy of Armbian is willing to test, I put together a script for using the H3's Cedar H264 acceleration to serve up an HLS stream page:
https://github.com/francistheodorecatte/...mer_hls.sh