Camera sensor probe sucess,but “media ctl -p” command can not see sensor device

Hi,
I find camera sensor imx390 probe sucess,but “media ctl -p” command can not see sensor device. How can I debug this problem?

hello xubin4952,

you’re woking with JP-5, right?
may I double confirm which Jetpack release version you’re now working with.

according to the logs, Device Registration should be completed.
is there any video nodes available? ($ ls -la /dev/video*)

Hi,
I forget the version.How can I confirm the version

according to the logs, [Device Registration]
I think sensor register is sucess.What else should I do to complete this?
Now I can see video node.

you may check release tag for confirmation, for instance, $ cat /etc/nv_tegra_release

Hi Jerry,
This is the version.Now how can I debug this problem?

hello xubin4952,

please refer to developer guide, Approaches for Validating and Testing the V4L2 Driver.
besides, the latest JP-5 release version is JP-5.1.3/r35.5.0, is it possible for moving to the latest release for verification?

Hi Jerry,
Thank you for your reply!
I have read Approaches for Validating and Testing the V4L2 Driver,I can not find some information about sensor probe sucess,I can not see information in “media-ctl -p”.

My version is R35.2.1 is not too old ,I think this version should work now.
Why should I change the version.

hello xubin4952,

we may need some logs for digging further.
I meant using V4L2 IOCTL directly to check basic camera functionality.
for example,
$ v4l2-ctl -d /dev/video0 --list-formats-ext
$ v4l2-ctl --set-fmt-video=width=1920,height=1080,pixelformat=RG10 --stream-mmap --stream-count=100 -d /dev/video0

HIi Jerry,
This is the information,do you have some ideas to debug this problem?
dmesg

v4l2-ctl -d /dev/video0 --list-formats-ext
image

media-ctl -p

v4l2-ctl --set-fmt-video=width=1920,height=1080,pixelformat=RG10 --stream-mmap --stream-count=100 -d /dev/video0

hello xubin4952,

may I double confirm what’s the device it is?
I’m curious why there’re multiple format types supported.

Hi Jerry,
My device is xavier AGX.

no… I meant your sensor device. it doesn’t look like a bayer raw camera sensor.

My sensor is IMX390,It seems I can not see this sensor in pipline in “media-ctl -p”.I think there are some error in my configuration。

hello xubin4952,

are you based-on reference camera driver for development?
for instance,
$public_sources/kernel_src/hardware/nvidia/platform/t19x/galen/kernel-dts/common/tegra194-p2822-0000-camera-imx390-a00.dtsi

as you can see…
it’s the driver for using SerDes (Serializer/Deserializer) chips, such as GMSL or FPD link.
did you also working with SerDes? did you confirm it’s also powered-on during kernel initialization stage?

Hi Jerry,
when I capture data, what does this error mean.

hello xubin4952,

here’re discarding frame errors report by VI, it means a failure capture state.
however, please check from hardware side to ensure it’s actually sending validate frames to CSI channel.

Hi,
I find it is a device tree config problem,
This is normal config will print bound,but my config can not bound.
What advice do you have for this problem ?

hello xubin4952,

here’s detail for device probing…
during kernel initialization stage, it’s step for camera device registration to setup a video device node to linux kernel. sensor probing only run once during kernel initialization stage of system boot-up.
for a typical camera application running cycle, the driver will Power On the sensor, Start Sensor Streaming, sending relevant v4l2 controls, and finally power off the sensor.
so, if there’s a error return, it’ll not register a video node, (i.e. /dev/video0).

you may see-also Topic 293662 and Topic 290610 to examine camera device registration process.