Problem with dual imx219

Robotics & Edge Computing Jetson & Embedded Systems Jetson Orin Nano
1

Good morning,
I have the same problem described in the following link

https://forums.developer.nvidia.com/t/jetpack-6-rev2-does-not-work-when-using-2-csi-cameras-imx219/302529

I have a new Orin Nano dev kit flashed throught SDKManager with the latest Jetpack version. I have two identical Rapberry Pi Camera V2 with imx219 sensor.
If I connect one camera to cam0 port it works, when I add a second camera to cam1 port, both the camera are recognized (i can see both /dev/video0 and /dev/video1) but only the camera connected to cam1 interface works.

I add the imx219-dual overlay through jetson-io utility.

In order to test the cam I use the following command

v4l2-ctl -c bypass_mode=0 --stream-mmap --stream-count=100 -d /dev/videoX

When I did the same thing to another Orin Nano dev kit flashed with Jetpack 5.1.4 both the camera worked

Any suggestion?

Regards

3

hello liviolima80,

just double check the carrier board you’re using.
is it Orin Nano Developer Kit out of box? or… you’ve connected Orin Nano module to any other carrier board?

4

Hi @JerryChang ,
I’m using the “official” “super” ( but actually the kit is exactly the same compared to another kit bought two years ago… ) Orin Nano Dev kit received two weeks ago… I flashed yesterday for the first time and attached to the cameras. Never moved the module to another board.

Regards

5

hello liviolima80,

just double check the L4T release version,
please examine the release tag, i.e. $ cat /etc/nv_tegra_release for verification.

besides, please also gather kernel init messages, i.e. $ dmesg > klogs.txt
we may check the logs of device registration.

6

Hi @JerryChang ,
these the info requested

cat /etc/nv_tegra_release
R36 (release), REVISION: 4.2, GCID: 38685322, BOARD: generic, EABI: aarch64, DATE: Fri Dec 13 00:16:27 UTC 2024
KERNEL_VARIANT: oot
TARGET_USERSPACE_LIB_DIR=nvidia
TARGET_USERSPACE_LIB_DIR_PATH=usr/lib/aarch64-linux-gnu/nvidia

Attached you can find the dmesg log

The strange thing I noticed is that when I connect two camera I have:

sudo dmesg | grep imx
[ 8.620598] imx219 9-0010: tegracam sensor driver:imx219_v2.0.6
[ 8.637588] tegra-camrtc-capture-vi tegra-capture-vi: subdev imx219 9-0010 bound
[ 8.667005] imx219 10-0010: tegracam sensor driver:imx219_v2.0.6
[ 8.683156] tegra-camrtc-capture-vi tegra-capture-vi: subdev imx219 10-0010 bound

but only the camera connected to cam1 interface works.

When I disconnect the camera attached to cam1 interface and I left only the camera attache to cam0 interface, the camera works correctly and I had

sudo dmesg | grep imx
[ 9.518123] imx219 9-0010: tegracam sensor driver:imx219_v2.0.6
[ 9.529412] imx219 9-0010: imx219_board_setup: error during i2c read probe (-121)
[ 9.534585] imx219 9-0010: board setup failed
[ 9.534637] imx219: probe of 9-0010 failed with error -121
[ 9.538585] imx219 10-0010: tegracam sensor driver:imx219_v2.0.6
[ 9.555842] tegra-camrtc-capture-vi tegra-capture-vi: subdev imx219 10-0010 bound

I expected the opposite behaviour, that camera connected to cam0 was i2c 9-0010 and the camera connected to cam1 interface was 10-0010
klogs.txt (62.5 KB)

9

hello liviolima80,

did you flashing the target with jetson-orin-nano-devkit-super.conf config file on r36.4.2?
please refer to Topic 317755, it’s known Jetson-IO issue with super mode config, the fixes will be available in the next Jetpack public release.

11

Hi @JerryChang ,
I flashed the board using SDK Manager GUI.

Then, since I realized that in “super” mode Jetson-IO script does not work, I fixed the problem as described in my reply of this post

https://forums.developer.nvidia.com/t/jetson-orin-nano-8gb-developer-kit-not-letting-me-run-jetson-io-py/319158/7

Next, I used Jetson-IO script to enable imx-219-dual camera configuration and I tried connecting two cameras, experiencing the issue of this post

12

hello liviolima80,

may I know what’s the modification you’ve done?
for instance, did you add compatible strings to support IMX219 with super config?

anyways,
we’ve verified r36.4.2 with jetson-orin-nano-devkit.conf on Orin-Nano plus two IMX219s.

13

Hi @JerryChang ,
I copy below my reply to the other post:

Hi @simon.bunn ,
I had the same issue with latest version of Jetpack. If you see other posts, you can see that this is some bug related to the dtb file of the new “super” mode. Nvida team seems that will fix in next release. In the meantime I found the following workaround:
- create a new boot configuration in /boot/extlinux/extlinux.conf copying from the default primary
- add in new configuration the following line
FDT /boot/dtb/kernel_tegra234-p3768-0000+p3767-0005-nv.dtb

where the file /boot/dtb/kernel_tegra234-p3768-0000+p3767-0005-nv.dtb is a copy of /boot/tegra234-p3768-0000+p3767-0005-nv.dtb

- reboot the board and select the new boot option
- when the system start you can succesfully run jetson-io.py

Basically with this fix you use the kit without the new super mode

14

Hi @JerryChang ,
I solve my issue. It was an error related to camera power supply…

15

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.