Hi team,
Should we enable the sensor dtsi files in tegra194-p3509-0000-a00.dtsi in order to work on overlay ?
I don’t know what does this question mean. Overlay is just a syntax and mechanism that to overwrite device tree during runtime. Enabling overlay and sensor dtsi are not related.
I can use overlay to enable display dtsi, pcie dtsi or any kind of dtsi. It does not limit to sensor dtsi.
HI @WayneWWW ,
- In this image (tegra194-p3509-0000-a00.dtsi file), I have enabled both imx477 and imx334 dtsi files . Should these files be included while working on overlay?
- I have created the below dts which includes imx334 & imx477 ,I copied the dtbo of this file to /boot/ when i select this dual sensors by using
sudo /opt/nvidia/jetson-io/config-by-hardware.py -n 2="Camera IMX477-A and IMX334-B"I could not find the user-custom dtb generated.
tegra194-p3668-all-p3509-0000-camera-imx477-imx334.zip (1.1 KB)
Just to clarify. So your question here is how to use overlay to enable imx477/imx334 camera?
yes @WayneWWW .
I have gone through the process mentioned in the website on how to enable the camera sensor by using jetson io tool ,but got struck at generating user-custom dtb , I like to know whether I am doing it correctly.
hello spavan,
please refer to Release Notes r35.6.0 of [4.2. Device Registration] for details.
Hi @JerryChang ,I have already gone through this notes .
I am using the below path to include the dts file.
hardware/nvidia/platform/t19x/jakku/kernel-dts
And i am using jetson-io tool as i mentioned above , i could not generate the user custom dtb file.
hello spavan,
may I know how you develop your camera overlay file?
please see-also AGX Xavier’s dual IMX274 reference driver.
for instance,
$public_sources/kernel_src/hardware/nvidia/platform/t19x/galen/kernel-dts/tegra194-p2822-camera-dual-imx274-overlay.dts
I have written a dts file by referring (tegra194-p3668-all-p3509-0000-camera-imx477-imx219.dts) from sources/hardware/nvidia/platform/t19x/jakku/kernel-dts path and converted into dtbo .After pushing dtbo into boot folder I could see the sensor on the list using jetson io tool .
tegra194-p3668-all-p3509-0000-camera-imx477-imx334.zip (1.1 KB)
hello spavan,
it looks these two were contradictions.
Can you elaborate why are they contradiction ? After the selecting the sensor from the list , user custom dtb needs to be generated but it is not generating.
I found that /dev/video0 is not created for imx334 ? is this causing any issue on generating user-custom-dtb file?
hello spavan,
I see, please share the kernel init messages for reference.
please check whether there’s any failure of device registration.
dmesg_logs.txt (65.0 KB)
I have attached the dmesg logs .
I could see the device bounded in the dmesg logs as well as i2cdetect.
hello spavan,
is this dual camera setup?
according to the logs… one of IMX334 has registered to system, but the other has reported with probing error.
[ 11.691022] imx334 9-0010: tegracam sensor driver:imx334_v2.0.6
[ 11.702556] tegra-camrtc-capture-vi tegra-capture-vi: subdev imx334 9-0010 bound
[ 11.709285] imx334 10-0010: tegracam sensor driver:imx334_v2.0.6
[ 11.710683] imx334 10-0010: imx334_board_setup: error during i2c read probe (-121)
[ 11.711293] imx334 10-0010: board setup failed
[ 11.711527] imx334: probe of 10-0010 failed with error -121
anyways, you should at least have /dev/video0 created, right?
please check… $ v4l2-ctl -d /dev/video0 --list-formats-ext
you may see-also Applications Using V4L2 IOCTL Directly,
please use V4L2 IOCTL to verify basic camera functionality,
for instance,
$ v4l2-ctl -d /dev/video0 --set-fmt-video=width=1920,height=1080,pixelformat=RG10 --set-ctrl bypass_mode=0 --stream-mmap --stream-count=100
Without /dev/video0 how can i check with these commands.
hello spavan,
did you meant a video node, /dev/video0 has not created?
there should be something wrong with the port bindings.
please refer to Verifying the V4L2 Sensor Driver, and Debugging Tips section to examine your sensor driver.
yes /dev/video0 is not created.
please debug the sensor driver and also device tree accordingly.
tegra_files.zip (2.3 KB)
These are two files in custom board and devkit , the sensor is working with custom board but not working with devkit.
hello spavan,
okay, please double check sensor device tree, especially the port bindings.