UNSOLVED VEYE-MIPI-IMX462 on Seeed J401 Carrier Board + Orin Nano 4GB (JetPack 6.2 / L4T 36.4.3) – No /dev/video Device Detected

joe

Dear Support Team,

I’m trying to get the VEYE-MIPI-IMX462 camera working on the Seeed Studio J401 carrier board using a Jetson Orin Nano 4GB running JetPack 6.2 (L4T 36.4.3).

I had previously set this up successfully on the Orin Nano Developer Kit, but I’m encountering issues with the J401 carrier board.

Issue Summary:
Initially, the camera was not being detected at all. After reviewing related posts on the forum, I found that a USB firmware update is required for compatibility with VEYE cameras on the J401. I followed the instructions provided here:

https://wiki.seeedstudio.com/Solution_for_the_Compatibility_Issue_between_reComputer_and_VEYE_Camera/

After applying the update, the camera appears to be detected according to the dmesg output:

dmesg | grep veye
[ 12.510227] veyecam 9-003b: probing v4l2 sensor
[ 12.510462] veyecam 9-003b: tegracam sensor driver:veyecam_v2.0.6
[ 12.525207] veyecam 9-003b: camera id is veyecam
[ 12.525824] veyecam 9-003b: sensor is IMX462
[ 12.525829] veyecam 9-003b: board type is ONE board
[ 12.526117] veyecam 9-003b: check hdver 7
[ 12.526464] tegra-camrtc-capture-vi tegra-capture-vi: subdev veyecam 9-003b bound
[ 12.526468] veyecam 9-003b: Detected VEYECAM sensor
[ 12.531848] veyecam 10-003b: probing v4l2 sensor
[ 12.531985] veyecam 10-003b: tegracam sensor driver:veyecam_v2.0.6
[ 12.541616] veyecam 10-003b: probe failed
[ 12.541623] veyecam 10-003b: board setup failed

Note: Camera at 10-003b is not physically connected, so its failure is expected.

Problem:
Despite the sensor being detected, no video device (e.g., /dev/video0 or /dev/video1) shows up in the system.

Configuration Details:
Here is the relevant section from /boot/extlinux/extlinux.conf:

LABEL primary
MENU LABEL primary kernel
LINUX /boot/Image
INITRD /boot/initrd
APPEND ${cbootargs} root=PARTUUID=fd3507f9-7b1c-48fb-a981-9fbbe6d30d9a rw rootwait rootfstype=ext4 mminit_loglevel=4 console=ttyTCU0,115200 firmware_class.path=/etc/firmware fbcon=map:0 nospectre_>
FDT /boot/dtb/kernel_tegra234-j401-p3768-0000+p3767-0004-recomputer.dtb
OVERLAYS /boot/veyecam/tegra234-p3767-camera-p3768-veyecam2m-dual.dtbo

I also followed the JetPack 6.x setup guide as described in the official VEYE documentation:
https://wiki.veye.cc/index.php/How_to_upgrade_the_Jetson_system_to_support_VEYE_cameras#For_Jetpack6.x_2

Questions:
What could be preventing /dev/video0 from being created, even though the sensor is detected by the kernel?

In the past, on the Orin Nano Developer Kit, I used both the VEYE-MIPI-IMX462 and the RAW-MIPI-AR0234M simultaneously with your assistance by applying this device tree overlay:

https://forum.veye.cc/topic/621/different-modules-simultaneously-on-jetson-nano-mipi-interface
→ tegra234-p3767-camera-p3768-veyecam2m-raw_ar0234m.dtbo

Can I reuse this DTBO with JetPack 6.2 and the J401 carrier board, or is there a specific overlay I should use for this combination?

Thank you for your support!
Looking forward to your guidance.

Best regards,
Joe

veye_xumm

@joe

@joe said in VEYE-MIPI-IMX462 on Seeed J401 Carrier Board + Orin Nano 4GB (JetPack 6.2 / L4T 36.4.3) – No /dev/video Device Detected:

Questions:
What could be preventing /dev/video0 from being created, even though the sensor is detected by the kernel?

Under normal circumstances, as long as the I2C communication is working, the /dev/video0 node should be generated properly. Based on my initial assessment, your issue likely stems from differences in the usage of MIPI CSI pins between the J401 carrier board and NVIDIA's official developer kit when paired with the Orin Nano core module. Since our DTBO is based on the device tree of NVIDIA's official developer board, it may not be fully compatible with the J401 out of the box. You can try analyzing the full dmesg output to identify any errors. I suggest reaching out to Seeed for further assistance on this issue.

joe

@veye_xumm
As you advised, I contacted Seeed Studio support for assistance. Their official response has made the situation clear. In short, Seeed Studio has confirmed they cannot and will not support the VEYE IMX462 camera on their J401 carrier board.

Since the carrier board is the source of the incompatibility (due to its lack of support for your sensor in its device tree and drivers), I now need your help to find a working solution.

Could you please provide a list of carrier boards for the Jetson Orin Nano module that you have tested and verified to be fully compatible with the VEYE IMX462 camera?

Furthermore, I need to ensure that whichever carrier board is recommended has at least two MIPI CSI-2 connectors to run the IMX462 and AR0234 cameras together.

Thank you for your time and support. I look forward to your detailed recommendations.

veye_xumm

@joe
Regarding the I2C issue with the J401 baseboard, we have previously resolved it, and the engineers at Seeed Studio have documented the solution on their wiki. Here are two links for your reference.

https://wiki.seeedstudio.com/Solution_for_the_Compatibility_Issue_between_reComputer_and_VEYE_Camera/

https://forum.veye.cc/topic/539/imx327s-with-recomputer-xavier-nano/10

joe

@veye_xumm
As I detailed in my initial post, I have already successfully applied that exact solution. The USB firmware update from that link is what allowed the kernel to detect the sensor, as shown by the dmesg | grep veye output I included.

The current state is:

-The USB firmware update is applied.

-The kernel probe is successful for the connected camera at 9-003b.

-The sensor is correctly identified as IMX462.

-The problem persists: No /dev/video0 device node is created.