• Re-flashed my Orin with the NVIDIA SDK manager
• Changed the CSI cable with the second cable that was provided by you guys. I also ensured the black tab on the Jetson Orin was facing 'up' while the pins on the wider end of the CSI cable that went to the IMX462 was facing 'towards' the tab (Please see pictures below for reference)

• And below are the steps that I took that eventually lead to the same probing error that was mentioned earlier

wget https://github.com/veyeimaging/nvidia_jetson_veye_bsp/releases/latest/download/nvidia_jetson_veye_bsp.tar.gz

tar -xzvf nvidia_jetson_veye_bsp.tar.gz

sudo cp -r nvidia_jetson_veye_bsp/ko/$(uname -r)/* /lib/modules/$(uname -r)/kernel/drivers/media/i2c/ -f

sudo depmod


sudo cp -r nvidia_jetson_veye_bsp/ko/5.15.148-tegra-l4t36.4.4/downstream/i2c/* /lib/modules/$(uname -r)/updates/drivers/media/i2c/ -f

sudo cp -r nvidia_jetson_veye_bsp/ko/5.15.148-tegra-l4t36.4.4/downstream/terga-camera/tegra-camera.ko /lib/modules/$(uname -r)/updates/drivers/media/platform/tegra/camera -f

sudo cp nvidia_jetson_veye_bsp/ko/5.15.148-tegra-l4t36.4.4/upstream/*.ko /lib/modules/$(uname -r)/kernel/drivers/media/v4l2-core/ -f

sudo depmod

ls /boot/dtb
# Output : kernel_tegra234-p3768-0000+p3767-0005-nv-super.dtb

# Create veyecam directory
sudo mkdir -p /boot/veyecam

# Copy the IMX462 overlay from JetPack 6.2.1 directory
sudo cp nvidia_jetson_veye_bsp/dtbs/Orin/JetPack_6.2.1_Linux_JETSON_ORIN_TARGETS/orin_nx_nano/tegra234-p3767-camera-p3768-veyecam2m-dual.dtbo /boot/veyecam/

sudo nano /boot/extlinux/extlinux.conf

################## Output from extlinux.conf file ##################

TIMEOUT 30
DEFAULT primary

MENU TITLE L4T boot options

LABEL primary
      MENU LABEL primary kernel
      LINUX /boot/Image
      # FDT line added 1/6/25
      INITRD /boot/initrd
      FDT /boot/dtb/kernel_tegra234-p3768-0000+p3767-0005-nv-super.dtb
      APPEND ${cbootargs} root=PARTUUID=4467ef34-b907-4537-8470-c873fa849134 rw rootwait rootfstype=ext4 mminit_loglevel=4 console=ttyTCU0,115200 firmware_class.path=/etc/firmware fbcon=map:0 video=efifb:off console=tty0 nv-auto-config
      # IMX462
      OVERLAYS /boot/veyecam/tegra234-p3767-camera-p3768-veyecam2m-dual.dtbo
# When testing a custom kernel, it is recommended that you create a backup of
# the original kernel and add a new entry to this file so that the device can
# fallback to the original kernel. To do this:
#
# 1, Make a backup of the original kernel
#      sudo cp /boot/Image /boot/Image.backup
#
# 2, Copy your custom kernel into /boot/Image
#
# 3, Uncomment below menu setting lines for the original kernel
#
# 4, Reboot

# LABEL backup
#    MENU LABEL backup kernel
#    LINUX /boot/Image.backup
#    INITRD /boot/initrd
#    APPEND ${cbootargs}

LABEL primary-backup
      MENU LABEL primary kernel backup
      LINUX /boot/Image
      FDT /boot/dtb/kernel_tegra234-p3768-0000+p3767-0005-nv-super.dtb
      INITRD /boot/initrd
      APPEND ${cbootargs} root=PARTUUID=4467ef34-b907-4537-8470-c873fa849134 rw rootwait rootfstype=ext4 mminit_loglevel=4 console=ttyTCU0,115200 firmware_class.path=/etc/firmware fbcon=map:0 video=efifb:off console=tty0 nv-auto-config
      OVERLAYS /boot/veyecam/tegra234-p3767-camera-p3768-veyecam2m-dual.dtbo

#######################################################################
sudo apt-mark hold nvidia-l4t-kernel nvidia-l4t-kernel-dtbs

sudo reboot

After restarting the Orin, I got the following dmesg output

sudo dmesg | grep veyecam
[   11.201520] veyecam 9-003b: probing v4l2 sensor
[   11.201648] veyecam 9-003b: tegracam sensor driver:veyecam_v2.0.6
[   11.211991] veyecam 9-003b: probe failed
[   11.212000] veyecam 9-003b: board setup failed
[   11.212329] veyecam 10-003b: probing v4l2 sensor
[   11.212455] veyecam 10-003b: tegracam sensor driver:veyecam_v2.0.6
[   11.227303] veyecam 10-003b: probe failed
[   11.227310] veyecam 10-003b: board setup failed

I did my best to be as thorough as possible, but at this point I'm not sure what else I could be missing

@d_101 said in Jetson Nano Orin IMX462:

Since I only have one IMX462 and you instructed me to
The only veyecam2m-labeled DTBO file that I assumed I need to use tegra234-p3767-camera-p3768-veyecam2m-dual.dtbo

Is that correct?

Yes.

Sorry, the Wiki article was not clear enough. We'll work on improving it.

@d_101

1. I think your hardware connections are correct. Also, the Dupont wires are generally not required.

2. I believe there are some issues with your operations on the .ko and .dtb files. Let me explain in detail below:
   Your camera model is VEYE-MIPI-IMX462, which is a color camera. You should only use the veyecam2m-labeled DTBO and veyecam.ko. There is no need to update the .ko files in the downstream and upstream directories.

3. However, judging from the dmesg output, it seems that you have also performed some correct steps, because the command dmesg | grep veye shows that the driver has been loaded correctly and has attempted to probe the camera.

Overall, I think there are some minor issues in your operations, but the general approach seems to be correct. Based on the following information:

# Checking dmesg
[   10.758731] veyecam 9-003b: probing v4l2 sensor
[   10.758853] veyecam 9-003b: tegracam sensor driver: veyecam_v2.0.6
[   10.771484] veyecam 9-003b: probe failed
[   10.771489] veyecam 9-003b: board setup failed
[   10.776701] veyecam 10-003b: probing v4l2 sensor
[   10.776828] veyecam 10-003b: tegracam sensor driver: veyecam_v2.0.6
[   10.787671] veyecam 10-003b: probe failed
[   10.787678] veyecam 10-003b: board setup failed

I can only suspect a hardware issue. Please remove the Dupont wires, or try using a different MIPI port.

Responding to " You should only use the veyecam2m-labeled DTBO" I see the following in the dtbs directory

bash

ct@ct-orin:~/nvidia_jetson_veye_bsp/dtbs/Orin/JetPack_6.2.1_Linux_JETSON_ORIN_TARGETS/orin_nx_nano$ ls
Makefile-JP6.1
Makefile-JP6.2
README
tegra234-camera-rbpcv3-csimx307.dtsi
tegra234-camera-rbpcv3-cssc132.dtsi
tegra234-camera-rbpcv3-veyecam2m-0x22.dtsi
tegra234-camera-rbpcv3-veyecam2m.dtsi
tegra234-camera-rbpcv3-veyecam2m_mvcam.dtsi
tegra234-camera-rbpcv3-veye_gxcam.dtsi
tegra234-camera-rbpcv3-veyeimx335.dtsi
tegra234-camera-rbpcv3-veye_mvcam-4lane-cam0.dtsi
tegra234-camera-rbpcv3-veye_mvcam-4lane-cam1-0.dtsi
tegra234-camera-rbpcv3-veye_mvcam-4lane-cam1.dtsi
tegra234-camera-rbpcv3-veye_mvcam.dtsi
tegra234-fpdlink-dual-90ub954.dtsi
tegra234-p3767-camera-p3768-csimx307-dual.dtbo
tegra234-p3767-camera-p3768-csimx307-dual.dts
tegra234-p3767-camera-p3768-cssc132-dual.dtbo
tegra234-p3767-camera-p3768-cssc132-dual.dts
tegra234-p3767-camera-p3768-raw_ar0234m-dual-4lane-cam1.dtbo
tegra234-p3767-camera-p3768-raw_ar0234m-dual-4lane-cam1.dts
tegra234-p3767-camera-p3768-raw_ar0234m-dual.dtbo
tegra234-p3767-camera-p3768-raw_ar0234m-dual.dts
tegra234-p3767-camera-p3768-raw_imx462m-dual.dtbo
tegra234-p3767-camera-p3768-raw_imx462m-dual.dts
tegra234-p3767-camera-p3768-veyecam2m-dual-0x22.dts
tegra234-p3767-camera-p3768-veyecam2m-dual.dtbo
tegra234-p3767-camera-p3768-veyecam2m-dual.dts
tegra234-p3767-camera-p3768-veyecam2m-fpdlink-dual.dtbo
tegra234-p3767-camera-p3768-veyecam2m-fpdlink-dual.dts
tegra234-p3767-camera-p3768-veyecam2m-raw_ar0234m.dts
tegra234-p3767-camera-p3768-veye_gxcam-dual.dtbo
tegra234-p3767-camera-p3768-veye_gxcam-dual.dts
tegra234-p3767-camera-p3768-veyeimx335-dual.dtbo
tegra234-p3767-camera-p3768-veyeimx335-dual.dts
tegra234-p3767-camera-p3768-veye_mvcam-dual-4lane-cam1.dtbo
tegra234-p3767-camera-p3768-veye_mvcam-dual-4lane-cam1.dts
tegra234-p3767-camera-p3768-veye_mvcam-dual.dtbo
tegra234-p3767-camera-p3768-veye_mvcam-dual.dts

My question is

• The only .dtbo file that looks right is the /tegra234-p3767-camera-p3768-veyecam2m-dual.dtbo which I did add to my extlinux.conf file as stated below

TIMEOUT 30
DEFAULT primary

MENU TITLE L4T boot options

LABEL primary
      MENU LABEL primary kernel
      LINUX /boot/Image
      # FDT line added 1/6/25
      FDT /boot/dtb/kernel_tegra234-p3768-0000+p3767-0005-nv-super.dtb
      INITRD /boot/initrd
      APPEND ${cbootargs} root=PARTUUID=4467ef34-b907-4537-8470-c873fa849134 rw rootwait rootfstype=ext4 mminit_loglevel=4 console=ttyTCU0,115200 firmware_class.path=/etc/firmware fbcon=map:0 video=efifb:off console=tty0 nv-auto-config
      # IMX462
      OVERLAYS /boot/veyecam/tegra234-p3767-camera-p3768-veyecam2m-dual.dtbo

# When testing a custom kernel, it is recommended that you create a backup of
# the original kernel and add a new entry to this file so that the device can
# fallback to the original kernel. To do this:
#
# 1, Make a backup of the original kernel
#      sudo cp /boot/Image /boot/Image.backup
#
# 2, Copy your custom kernel into /boot/Image
#
# 3, Uncomment below menu setting lines for the original kernel
#
# 4, Reboot

# LABEL backup
#    MENU LABEL backup kernel
#    LINUX /boot/Image.backup
#    INITRD /boot/initrd
#    APPEND ${cbootargs}

LABEL primary-backup
      MENU LABEL primary kernel backup
      LINUX /boot/Image
      FDT /boot/dtb/kernel_tegra234-p3768-0000+p3767-0005-nv-super.dtb
      INITRD /boot/initrd
      APPEND ${cbootargs} root=PARTUUID=4467ef34-b907-4537-8470-c873fa849134 rw rootwait rootfstype=ext4 mminit_loglevel=4 console=ttyTCU0,115200 firmware_class.path=/etc/firmware fbcon=map:0 video=efifb:off console=tty0 nv-auto-config
      OVERLAYS /boot/veyecam/tegra234-p3767-camera-p3768-veyecam2m-dual.dtbo

My question here is

• Last listed in the directory above I only see tegra234-p3767-camera-p3768-veyecam2m-dual.dtbo and tegra234-camera-rbpcv3-veyecam2m.dtsi that come close to what you instructed earlier regarding me using the veyecam2m that was labeled with DTBO
• Since I only have one IMX462 and you instructed me to
  The only veyecam2m-labeled DTBO file that I assumed I need to use tegra234-p3767-camera-p3768-veyecam2m-dual.dtbo

Is that correct?

Also, responding to the comment you made earlier regarding updating the .ko files up/downstream

There is no need to update the `.ko` files in the **downstream** and **upstream** directories.

It is stated in the wiki page to do just that

Therefore, for Jetpack 6.2.1, the following commands should be modified as:

sudo cp nvidia_jetson_veye_bsp/ko/5.15.148-tegra-l4t36.4.4/downstream/i2c/* /lib/modules/$(uname -r)/updates/drivers/media/i2c/ -f

sudo cp nvidia_jetson_veye_bsp/ko/5.15.148-tegra-l4t36.4.4/downstream/terga-camera/tegra-camera.ko /lib/modules/$(uname -r)/updates/drivers/media/platform/tegra/camera -f

sudo cp nvidia_jetson_veye_bsp/ko/5.15.148-tegra-l4t36.4.4/upstream/*.ko /lib/modules/$(uname -r)/kernel/drivers/media/v4l2-core/ -f

If those steps aren't necessary for someone who's running Jetpack 6.2.1 I feel like it should be removed to lessen the confusion since the wiki page instructions aren't the easiest to follow in my opinion.

1. I think your hardware connections are correct. Also, the Dupont wires are generally not required.

2. I believe there are some issues with your operations on the .ko and .dtb files. Let me explain in detail below:
   Your camera model is VEYE-MIPI-IMX462, which is a color camera. You should only use the veyecam2m-labeled DTBO and veyecam.ko. There is no need to update the .ko files in the downstream and upstream directories.

3. However, judging from the dmesg output, it seems that you have also performed some correct steps, because the command dmesg | grep veye shows that the driver has been loaded correctly and has attempted to probe the camera.

Overall, I think there are some minor issues in your operations, but the general approach seems to be correct. Based on the following information:

# Checking dmesg
[   10.758731] veyecam 9-003b: probing v4l2 sensor
[   10.758853] veyecam 9-003b: tegracam sensor driver: veyecam_v2.0.6
[   10.771484] veyecam 9-003b: probe failed
[   10.771489] veyecam 9-003b: board setup failed
[   10.776701] veyecam 10-003b: probing v4l2 sensor
[   10.776828] veyecam 10-003b: tegracam sensor driver: veyecam_v2.0.6
[   10.787671] veyecam 10-003b: probe failed
[   10.787678] veyecam 10-003b: board setup failed

I can only suspect a hardware issue. Please remove the Dupont wires, or try using a different MIPI port.