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

@veye_xumm
I noticed that there is no difference when I change the order of '-b 10' to the end of the line in the command. I'm running the command from ~/nvidia_jetson_veye_bsp/i2c_cmd/bin; can you confirm if this path is correct? Additionally, I'm open to any alternative solutions or suggestions. Thanks in advance for your help!

@veye_xumm
It seems that the parameters I've configured are retaining their previous values:

./veye_mipi_i2c.sh -b 10 -r -f mshutter
r mshutter is 0x 0
./veye_mipi_i2c.sh -b 10 -w -f mshutter -p1 0x44
w mshutter is 0x44
./veye_mipi_i2c.sh -b 10 -r -f mshutter
r mshutter is 0x 0

or

./veye_mipi_i2c.sh -b 10 -r -f mirrormode
r mirrormode is 0x 0
./veye_mipi_i2c.sh -b 10 -w -f mirrormode -p1 0x02
w mirrormode is 0x 2
./veye_mipi_i2c.sh -b 10 -r -f mirrormode
r mirrormode is 0x 0

Am I making a mistake somewhere?

@veye_xumm

The results:

./veye_mipi_i2c.sh -r -f hdver -b 9
hardware version is 0x 1
release date is 20 1- 1- 1

./veye_mipi_i2c.sh -r -f hdver -b 10
hardware version is 0x 7
release date is 20 0- 0- 0

@veye_xumm
Thank you for your online response.
What about my second question. Have I do something wrong that the values of parameters do not set?
./veye_mipi_i2c.sh -b 9 -r -f mshutter
r mshutter is 0x 1
./veye_mipi_i2c.sh -b 9 -w -f mshutter -p1 0x44
w mshutter is 0x44
./veye_mipi_i2c.sh -b 9 -r -f mshutter
r mshutter is 0x 1
It have the fix value every time i get it!

Thank you for your ongoing support

@veye_xumm
Thank you for your prompt response.
I'm currently facing two issues while using the I2C script to set parameters from the specified path: nvidia_jetson_veye_bsp/i2c_cmd/bin/veye_mipi_i2c.sh .

1- Firstly, the document link provided (https://wiki.veye.cc/index.php/I2c_bus_number_and_video_node) does not specify the appropriate -b parameter for Orin Nano. To identify the correct bus number, I executed the following command:
ls -ltrh /sys/bus/i2c/devices/i2c*
lrwxrwxrwx 1 root root 0 Mar 15 2023 /sys/bus/i2c/devices/i2c-2 -> ../../../devices/platform/3180000.i2c/i2c-2
lrwxrwxrwx 1 root root 0 Mar 15 2023 /sys/bus/i2c/devices/i2c-9 -> ../../../devices/platform/3180000.i2c/i2c-2/i2c-9
lrwxrwxrwx 1 root root 0 Mar 15 2023 /sys/bus/i2c/devices/i2c-8 -> ../../../devices/platform/31e0000.i2c/i2c-8
lrwxrwxrwx 1 root root 0 Mar 15 2023 /sys/bus/i2c/devices/i2c-7 -> ../../../devices/platform/c250000.i2c/i2c-7
lrwxrwxrwx 1 root root 0 Mar 15 2023 /sys/bus/i2c/devices/i2c-6 -> ../../../devices/platform/31c0000.i2c/i2c-6
lrwxrwxrwx 1 root root 0 Mar 15 2023 /sys/bus/i2c/devices/i2c-5 -> ../../../devices/platform/31b0000.i2c/i2c-5
lrwxrwxrwx 1 root root 0 Mar 15 2023 /sys/bus/i2c/devices/i2c-4 -> ../../../devices/platform/bpmp/bpmp:i2c/i2c-4
lrwxrwxrwx 1 root root 0 Mar 15 2023 /sys/bus/i2c/devices/i2c-3 -> ../../../devices/platform/3190000.i2c/i2c-3
lrwxrwxrwx 1 root root 0 Mar 15 2023 /sys/bus/i2c/devices/i2c-10 -> ../../../devices/platform/3180000.i2c/i2c-2/i2c-10
lrwxrwxrwx 1 root root 0 Mar 15 2023 /sys/bus/i2c/devices/i2c-1 -> ../../../devices/platform/c240000.i2c/i2c-1
lrwxrwxrwx 1 root root 0 Mar 15 2023 /sys/bus/i2c/devices/i2c-0 -> ../../../devices/platform/3160000.i2c/i2c-0
lrwxrwxrwx 1 root root 0 Dec 19 05:26 /sys/bus/i2c/devices/i2c-11 -> ../../../devices/platform/13800000.display/i2c-11
Can you assist me in determining the appropriate -b parameter based on this information?

2- Secondly, although I can successfully read parameters, I encounter difficulties when attempting to set them. For instance:
./veye_mipi_i2c.sh -r -f mshutter
r mshutter is 0x1
./veye_mipi_i2c.sh -w -f mshutter -p1 0x44
w mshutter is 0x44
./veye_mipi_i2c.sh -r -f mshutter
r mshutter is 0x1
It appears that the parameter is not being set successfully, as reading it after the supposed update returns the default value. Could you guide me on where I might be going wrong in the parameter-setting process?
I appreciate your assistance in advance.