OV5640 camera module reg read error

[FrancisTheodoreCat]

Hm, it's probably down to the video color space format. I know the Cedar accelerator can only handle NV12 and NV16 color spaces, but I don't know what the equivalent V4L2 format is. I'll poke at it more once I get a working camera on my PineCube.

edit:
Try the updated script. I did some more reading on color space stuff, and I think I got it right. Also removed the x/raw bit of the pipeline that cedarh264enc didn't like. gstreamer now only spits out the following:

0:00:01.044829353  1974  0x1dda840 ERROR          cedar_h264enc gstcedarh264enc.c:340:gst_cedarh264enc_change_state: Cannot open VE

Along with the ever-present dmesg errors:

[ 1511.713485] ov5640 1-003c: ov5640_read_reg: error: reg=300a
[ 1511.713504] ov5640 1-003c: ov5640_set_power_on: failed to read chip identifier

I will note,  media-ctl --print-topology does show the camera on /dev/video0:

Media controller API version 5.10.0

Media device information
------------------------
driver          sun6i-csi
model          Allwinner Video Capture Device
serial         
bus info        platform:1cb4000.camera
hw revision    0x0
driver version  5.10.0

Device topology
- entity 1: sun6i-csi (1 pad, 1 link)
            type Node subtype V4L flags 0
            device node name /dev/video0
pad0: Sink
<- "ov5640 1-003c":0 [ENABLED]

- entity 5: ov5640 1-003c (1 pad, 1 link)
            type V4L2 subdev subtype Sensor flags 0
            device node name /dev/v4l-subdev0
pad0: Source
[fmt:UYVY8_2X8/1920x1080@1/15 colorspacergb xferrgb ycbcr:601 quantization:full-range]
-> "sun6i-csi":0 [ENABLED]

All I can think is the camera module, or the CSI cable, is bad. Or both.