PinePhone Pro/IMX258 Camera Debugging problem

[jasperji]

I followed the command provided by the website[https://wiki.pine64.org/wiki/PinePhone_P..._Debugging] and ran.

Code:

"media-ctl" "-d" "platform:rkisp1" "-l" "'imx258 1-001a':0 -> 'rkisp1_isp':0 [1]"

return

Opening media device /dev/media0
Enumerating entities
looking up device: 81:8
looking up device: 81:9
looking up device: 81:10
looking up device: 81:2
looking up device: 81:3
looking up device: 81:6
looking up device: 81:7
looking up device: 81:11
looking up device: 81:12
Found 9 entities
Enumerating pads and links
no such entity "imx258 1-001a"
media_parse_setup_link: Unable to parse link

'imx258 1-001a':0 -> 'rkisp1_isp':0 [1]
  ^
Unable to parse link: Invalid argument (22)

run this command.

Code:

"v4l2-ctl" "-z" "platform:rkisp1" "-d" "rkisp1_selfpath" "--stream-mmap" "--stream-count" "1" "--verbose"

return

VIDIOC_QUERYCAP: ok

VIDIOC_REQBUFS returned 0 (Success)

VIDIOC_QUERYBUF returned 0 (Success)

VIDIOC_QUERYBUF returned 0 (Success)

VIDIOC_QUERYBUF returned 0 (Success)

VIDIOC_QUERYBUF returned 0 (Success)

VIDIOC_G_FMT returned 0 (Success)

VIDIOC_QBUF returned 0 (Success)

VIDIOC_QBUF returned 0 (Success)

VIDIOC_QBUF returned 0 (Success)

VIDIOC_QBUF returned 0 (Success)
VIDIOC_STREAMON returned -1 (Broken pipe)

My camera function is not working properly. 

system: Arch linux arm
Kernel：Linux 6.7.7-1-danctnix

[gtw]

The first error ("Unable to parse link") can happen on newer kernels because they introduce a new rkisp1_csi node in between the imx258 and ikisp1_isp (and so requesting a direct link no longer works).

The second error ("VIDIOC_STREAMON returned -1") is a symptom of the first: since the topology hasn't been configured properly, trying to start streaming over it won't work either.

I've updated the Wiki page you cite to give example commands that work for me on a 6.9 kernel.  Please see the page again, and hopefully the new version will help.

(Unfortunately, the rkisp1 driver seems to change frequently, so the example commands are rather fragile.  In general, deducing the correct commands for your particular driver version might require some interpretation of the "media-ctl -p" output.)