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

Thank you for building the DTBO! It works perfectly, and now I can access both /dev/video0 and /dev/video1. Streaming with the IMX462 works without any issues, but when I stream using the AR0234, the output shows a split view and looks green (see the attached image for reference).

Here is the command I used for streaming:

gst-launch-1.0 nvv4l2camerasrc device=/dev/video1 ! "video/x-raw(memory:NVMM),format=(string)UYVY, width=(int)1920, height=(int)1080" ! nvvidconv ! "video/x-raw(memory:NVMM),format=(string)I420" ! nv3dsink sync=false

@veye_xumm
Thank you so much for your willingness to assist with the dtbo compilation! I greatly appreciate your support and the effort you're putting into this. Please let me know if you need any additional details about my project or environment to facilitate the process.

@veye_xumm
I'm encountering difficulties building my custom Device Tree Source (DTS) on a Jetson Orin. I've modified the DTS file and am attempting to build it directly on the Orin using the dtc command.

However, I'm unable to locate the header file dt-bindings/tegra234-p3767-0000-common.h.

Could you please provide instructions, a link to a guide, or any relevant documentation on how to build DTS files on a Jetson Orin?

@veye_xumm
Hi, it's been a while.

I am looking to use the veye-mipi-imx462 and raw-mipi-ar0234m cameras together on the Jetson Orin Nano (JetPack 6.1/Orin Nano Super). Is the process the same as running both cameras on the Jetson Nano, or do I need to add two DTBO files to /boot/extlinux/extlinux.conf? I have successfully set up the veye-mipi-imx462 on the Orin Nano. What steps should I take to add the second camera?

Thanks!

Thank you for your response. I'm happy to hear this. I will try to test it as soon as I can and reply here.

Dear V-EYE support,

I would like to know if it is possible to connect and use two different camera modules simultaneously with a Jetson Nano via the MIPI interface. Specifically, I am interested in using the IMX462, AR234, or IMX265 modules.

Best regards,

Hello,

I'm trying to use the IMX462 v-eye camera with a Jetson Nano. My Jetpack version is 4.6. I followed the instructions on this link:
https://wiki.veye.cc/index.php/VEYE_CS_Camera_for_Jetson_TX2

After copying the "tegra210-p3448-0000-p3449-0000-b00.dtb" file to "/boot/veyecam" and making changes to the "/boot/extlinux/extlinux.conf" file, I restarted the board. However, I encountered the following error:

dmesg | grep veye
[ 2.436857] veyecam 7-003b: probing v4l2 sensor
[ 2.437085] veyecam 7-003b: tegracam sensor driver: veyecam_v2.0.6
[ 3.544132] veyecam 7-003b: probe failed 
[ 3.548192] veyecam 7-003b: board setup failed
[ 3.552794] veyecam 8-003b: probing v4l2 sensor
[ 3.553005] veyecam 8-003b: tegracam sensor driver: veyecam_v2.0.6
[ 3.563049] veyecam 8-003b: probe failed 
[ 3.567120] veyecam 8-003b: board setup failed

What should I check next?

Thank you for your support.

Best regards,
Joe

@joe
It is indicated in the documents about "New function list" that:
"The following new features are only supported in camera's firmware versions with release time later than 2022-11-22."
My firmware version is exactly 2022-11-22. Is this version support "New function list"?

@veye_xumm
It work, after change the mipi connector! (I use -b 9.)
Thanks