VEYE IMAGING Forum

Otca

based on https://wiki.veye.cc/index.php/RAW-MIPI-SC132M_Data_Sheet
11 ENABLE Camera Power Enable
The Voltage of PIN-11 is 1.74v

Otca

Hi, I have tested CSI-0 and CSI-1.
I'm using WeAct carrierBoard (N_002) with jetson orin nx(16GB)
I share the results with you to get to the solution faster.
thanks in advance for your consideration.

1. Version

sudo ./mv_mipi_i2c.sh -r -f version -b 9 
Executing: ./mv_mipi_i2c_new.sh -r version -b 9
version is C 01.04 and L 00.00

2. I2C-detect:

i2cdetect -y -r 9
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:                         -- -- -- -- -- -- -- -- 
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
30: -- -- -- -- -- -- -- -- -- -- -- UU -- -- -- -- 
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
70: -- -- -- -- -- -- -- --

3. Trigg mode

sudo ./mv_mipi_i2c.sh -r -f trgmode -b 9 
Executing: ./mv_mipi_i2c_new.sh -r trgmode -b 9
r trigger mode is 0

4. v4l2-ctl
doesnt work and I get the following messages in dmesg

 WIDTH=1080
export HEIGHT=1280
export FPS=50
v4l2-ctl --set-ctrl roi_x=0                        
v4l2-ctl --set-ctrl roi_y=0
v4l2-ctl --set-fmt-video=width=$WIDTH,height=$HEIGHT,pixelformat=GREY
v4l2-ctl --set-ctrl frame_rate=$FPS
v4l2-ctl --set-fmt-video=width=$WIDTH,height=$HEIGHT,pixelformat=GREY --stream-mmap --stream-count=-1 --stream-to=/dev/null

5. DMESG:

[   36.404093] mvcam 9-003b: csi2_try format
[   36.404109] mvcam 9-003b: mvcam_csi2_get_fmt_idx_by_code success
[   36.484983] mvcam 9-003b: csi2_try format
[   36.484996] mvcam 9-003b: mvcam_csi2_get_fmt_idx_by_code success
[   36.566999] mvcam 9-003b: camera_common_mclk_enable: no device power rail
[   36.567010] mvcam 9-003b: camera_common_s_power: failed to enable mclk
[   39.903309] tegra-camrtc-capture-vi tegra-capture-vi: uncorr_err: request timed out after 2500 ms
[   39.903335] tegra-camrtc-capture-vi tegra-capture-vi: err_rec: attempting to reset the capture channel
[   39.905050] tegra-camrtc-capture-vi tegra-capture-vi: err_rec: successfully reset the capture channel
[   42.463311] tegra-camrtc-capture-vi tegra-capture-vi: uncorr_err: request timed out after 2500 ms
[   42.463338] tegra-camrtc-capture-vi tegra-capture-vi: err_rec: attempting to reset the capture channel
[   42.464861] tegra-camrtc-capture-vi tegra-capture-vi: err_rec: successfully reset the capture channel
[   45.023322] tegra-camrtc-capture-vi tegra-capture-vi: uncorr_err: request timed out after 2500 ms
[   45.023351] tegra-camrtc-capture-vi tegra-capture-vi: err_rec: attempting to reset the capture channel
[   45.024651] tegra-camrtc-capture-vi tegra-capture-vi: err_rec: successfully reset the capture channel
[   47.583304] tegra-camrtc-capture-vi tegra-capture-vi: uncorr_err: request timed out after 2500 ms
[   47.583330] tegra-camrtc-capture-vi tegra-capture-vi: err_rec: attempting to reset the capture channel
[   47.584733] tegra-camrtc-capture-vi tegra-capture-vi: err_rec: successfully reset the capture channel
[   50.143315] tegra-camrtc-capture-vi tegra-capture-vi: uncorr_err: request timed out after 2500 ms
[   50.143348] tegra-camrtc-capture-vi tegra-capture-vi: err_rec: attempting to reset the capture channel
[   50.144429] tegra-camrtc-capture-vi tegra-capture-vi: err_rec: successfully reset the capture channel

6. sudo dmesg | grep -i mvcam

[   11.240305] mvcam 9-003b: veye mv series camera driver version: 01.01.06
[   11.941759] mvcam 9-003b: camera is: RAW-MIPI-SC132M
[   11.942058] mvcam 9-003b: firmware version: 0x1040000
[   11.950629] tegra-camrtc-capture-vi tegra-capture-vi: subdev mvcam 9-003b bound
[   11.982952] mvcam 10-003b: veye mv series camera driver version: 01.01.06
[   12.686081] veye_mvcam: mvcam_read: Reading register 0x04 failed
[   12.686095] mvcam 10-003b: failed to read chip id
[   12.686098] mvcam 10-003b: mvcam_identify_module failed.
[   36.404093] mvcam 9-003b: csi2_try format
[   36.404109] mvcam 9-003b: mvcam_csi2_get_fmt_idx_by_code success
[   36.484983] mvcam 9-003b: csi2_try format
[   36.484996] mvcam 9-003b: mvcam_csi2_get_fmt_idx_by_code success
[   36.566999] mvcam 9-003b: camera_common_mclk_enable: no device power rail
[   36.567010] mvcam 9-003b: camera_common_s_power: failed to enable mclk

7. V4l2-ctl

v4l2-ctl --list-formats-ext


ioctl: VIDIOC_ENUM_FMT
	Type: Video Capture

	[0]: 'GREY' (8-bit Greyscale)
		Size: Discrete 1080x1280
			Interval: Discrete 0.020s (50.000 fps)
	[1]: 'XY10' (XAVIER 10-bit/16-bit Greyscale)
		Size: Discrete 1080x1280
			Interval: Discrete 0.020s (50.000 fps)

8. Jetson Info

jtop 4.3.2 - (c) 2024, Raffaello Bonghi [raffaello@rnext.it]
Website: https://rnext.it/jetson_stats

 Platform                                    Serial Number: [s|XX CLICK TO READ XXX]
  Machine: aarch64                           Hardware
  System: Linux                               Model: NVIDIA Jetson Orin NX Engineering Reference Developer Kit
  Distribution: Ubuntu 22.04 Jammy Jellyfish  699-level Part Number: 699-13767-0000-300 M.1
  Release: 5.15.148-tegra                     P-Number: p3767-0000
  Python: 3.10.12                             Module: NVIDIA Jetson Orin NX (16GB ram)
                                              SoC: tegra234
 Libraries                                    CUDA Arch BIN: 8.7
  CUDA: 12.6.68                               L4T: 36.4.3
  cuDNN: 9.3.0.75                             Jetpack: 6.2
  TensorRT: 10.3.0.30
  VPI: 3.2.4                                 Hostname: jetson
  Vulkan: 1.3.204                            Interfaces
  OpenCV: 4.8.0 with CUDA: NO                 eno1: 192.168.0.113
                                              docker0: 172.17.0.1

Otca

@veye_xumm Thanks
my problem is solved.

Otca

@veye_xumm
Hi,
To set up the environment for the MV-MIPI camera series, I followed these steps:

Install the Driver
First, I downloaded and installed the V4L2 driver package:

sudo raspi-config
# Step 6.1: Download the driver package
wget https://github.com/veyeimaging/raspberrypi_v4l2/releases/latest/download/raspberrypi_v4l2.tgz

# Step 6.2: Install the driver
tar -xzvf raspberrypi_v4l2.tgz
cd raspberrypi_v4l2/release/
chmod +x *

# For Raspberry Pi 5
sudo ./install_driver_rpi5.sh veye_mvcam

List Supported Formats and Frame Rates
After setting up the driver, I used the v4l2-ctl command to verify the available formats and frame rates:

v4l2-ctl --list-formats-ext

This returned the following output:

ioctl: VIDIOC_ENUM_FMT
        Type: Video Capture

        [0]: 'MJPG' (Motion-JPEG, compressed)
                Size: Discrete 1920x1080
                        Interval: Discrete 0.033s (30.000 fps)
                Size: Discrete 160x120
                        Interval: Discrete 0.033s (30.000 fps)
                Size: Discrete 320x240
                        Interval: Discrete 0.033s (30.000 fps)
                Size: Discrete 352x288
                        Interval: Discrete 0.033s (30.000 fps)
                Size: Discrete 640x480
                        Interval: Discrete 0.033s (30.000 fps)
                Size: Discrete 800x600
                        Interval: Discrete 0.033s (30.000 fps)
                Size: Discrete 1024x768
                        Interval: Discrete 0.033s (30.000 fps)
                Size: Discrete 1280x720
                        Interval: Discrete 0.033s (30.000 fps)
                Size: Discrete 1280x960
                        Interval: Discrete 0.033s (30.000 fps)

        [1]: 'YUYV' (YUYV 4:2:2)
                Size: Discrete 1920x1080
                        Interval: Discrete 0.200s (5.000 fps)
                Size: Discrete 640x480
                        Interval: Discrete 0.033s (30.000 fps)
                Size: Discrete 1280x720
                        Interval: Discrete 0.125s (8.000 fps)
                Size: Discrete 800x600
                        Interval: Discrete 0.050s (20.000 fps)
                Size: Discrete 960x540
                        Interval: Discrete 0.067s (15.000 fps)
                Size: Discrete 1280x960
                        Interval: Discrete 0.125s (8.000 fps)

Measure Frame Rate
To test the frame rate, I ran the following command:

v4l2-ctl --set-fmt-video=width=1920,height=1080,pixelformat=MJPG --stream-mmap --stream-count=-1 --stream-to=/dev/null

<<<<<<<<<<<<<<<<<< 17.64 fps, dropped buffers: 1
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< 23.71 fps
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< 25.76 fps
<<<<<<<<<<<<<<<<<<<<<<<<<<<<< 26.75 fps
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< 27.38 fps
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< 27.79 fps
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< 28.09 fps
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< 28.32 fps
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< 29.88 fps
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< 29.88 fps
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< 29.88 fps
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< 29.88 fps
<<<<<<<<<<<<<<<<<<<<<<<<<<<<< 29.88 fps
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< 29.88 fps
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< 29.88 fps
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< 29.86 fps
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< 29.86 fps
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< 29.86 fps
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< 29.86 fps
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< 29.86 fps
<<<<<<<<<<<<<<<<<<<<<<<<<<<<< 29.88 fps
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< 29.88 fps

Otca

Hi,

I have set up the environment for the MV-MIPI camera series on a Raspberry Pi 5. Currently, I'm achieving a maximum frame rate of 30 FPS at the highest resolution (1920x1080) for both cameras.

In comparison, on a Jetson Orin NX:
The IMX-264 achieves 67 FPS.
The IMX-287 achieves approximately 500 FPS.
I would like to understand how to optimize the setup on the Raspberry Pi 5 to achieve higher frame rates, as the current 30 FPS seems limited compared to what is possible on the Jetson Orin NX.
Thanks in advance!

Otca

@veye_xumm
I think my connections are not as good as it should be.
I'll try in better condition if the problem persist, I'll make a new issue.
Thanks

Otca

I'm using the MV-MIPI-IMX264 and MV-MIPI-IMX287 sensors with the NVIDIA Jetson Orin NX, running JetPack 6 (R36.3), and I've noticed horizontal line artifacts in my images. This issue is especially noticeable with the IMX287 sensor and when I set a smaller Region Of Interest (ROI) on the IMX264 sensor.
Have any similar experience on this?
thanks

Screenshot from 2024-11-07 17-57-52.png

Otca

@otca Solved:

./mv_mipi_i2c.sh -r -f roi -b 9
./mv_mipi_i2c.sh -w -f roi -p1 0 -p2 0 -p3 1920 -p4 1080 -b 9
./mv_mipi_i2c.sh -r -f maxfps -b 9
./mv_mipi_i2c.sh -r -f fps -b 9
./mv_mipi_i2c.sh -w -f fps -p1 67 -b 9

Otca

@veye_xumm Sure, I'll Check it.
would mind helping me for getting Max FPS please?

export WIDTH=1920             
export HEIGHT=1080                                                                
export FPS=67                                                                                                                                                                              
v4l2-ctl --set-fmt-video=width=$WIDTH,height=$HEIGHT,pixelformat=GREY --stream-mmap --stream-count=-1 --stream-to=/dev/null
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< 30.00 fps
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< 30.00 fps
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< 30.00 fps
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< 30.00 fps

According to Veye Wiki, I can get 67 frames per second.

Would you please tell me what should I do in addition to get the highest FPS?
Thanks

Otca

@veye_xumm
I am experiencing an issue with CSI number 1. Specifically, it is not functioning properly on CSI-1, while everything works fine on CSI-0.
I would appreciate it if you could provide insight into why this might be happening. Additionally, I would like to mention that the vlc component is working without any issues, so the problem seems isolated to CSI-1 in my case.

v4l2-ctl --set-fmt-video=width=$WIDTH,height=$HEIGHT,pixelformat=GREY --stream-mmap --stream-count=-1 --stream-to=/dev/null
<<<<<<<<<<<<<<<<<<<<<<<<<<<<< 27.99 fps
<<<<<<<<<<<<<<<<<<<<<<<<<<<< 27.99 fps
<<<<<<<<<<<<<<<<<<<<<<<<<<<< 27.99 fps
<<<<<<<<<<<<<<<<<<<<<<<<<<<< 27.99 fps
<<<<<<<<<<<<<<<<<<<<<<<<<<<< 27.99 fps
<<<<<<<<<<<<<<<<<<<<<<<<<<<< 27.99 fps
<<<<<<<<<<<<<<<<<<<<<<<<<<<< 27.99 fps
<<<<<<<<<<<<<<<<<<<<<<<<<<<< 27.99 fps
<<<<<<<<<<<<<<<<<<<<<<<<<<<< 27.99 fps                                                                 
<<<<<<<<<<<<<<<<<<<<<<<<<<<< 27.99 fps                                                                 
<<<<<<<<<<<<<<<<<<<<<<<<<<<< 27.99 fps

In the End, I cannot express how truly grateful I am for all the assistance you've provided over the past two weeks. Your patience and dedication throughout the entire process have been remarkable. Thanks to your consistent help, everything is finally working perfectly, and I am incredibly appreciative of your efforts.

Once again, thank you so much for your unwavering support and understanding.

Otca

@veye_xumm said in NVidia Jetson Jetpack 6 support?:

sudo ./mv_mipi_i2c.sh -r -f trgmode -b 10

sure I will try other CSI port and my board is Jetson Orin NX DeveloperKit (16GB). It's supported by VEYE and Nvidia.

sudo ./mv_mipi_i2c.sh -r -f trgmode -b 10
r trigger mode is 0

I'll reboot and give you the result for other CSI

Otca

@veye_xumm said in NVidia Jetson Jetpack 6 support?:

sudo ./mv_mipi_i2c.sh -r -f version -b 10

sure!

sudo ./mv_mipi_i2c.sh -r -f version -b 10

version is C 01.41 and L 02.06

Otca

@veye_xumm Hi,
this is the results:
The following lines and corresponding Dmesg log:

export WIDTH=2432
export HEIGHT=2056
export FPS=28
v4l2-ctl --set-ctrl roi_x=0
v4l2-ctl --set-ctrl roi_y=0
v4l2-ctl --set-fmt-video=width=$WIDTH,height=$HEIGHT,pixelformat=GREY
v4l2-ctl --set-ctrl frame_rate=$FPS

Dmesg log:

[   84.571478] mvcam 10-003b: csi2_try format
[   84.571495] mvcam 10-003b: mvcam_csi2_get_fmt_idx_by_code success

and The last line didnt run successfully:

v4l2-ctl --set-fmt-video=width=$WIDTH,height=$HEIGHT,pixelformat=GREY --stream-mmap --stream-count=-1 --stream-to=/dev/null

####Dmesg of Last Line:
I terminated the above command after 10 seconds.

[  113.809582] mvcam 10-003b: csi2_try format
[  113.809604] mvcam 10-003b: mvcam_csi2_get_fmt_idx_by_code success
[  113.886292] mvcam 10-003b: camera_common_mclk_enable: no device power rail
[  113.886304] mvcam 10-003b: camera_common_s_power: failed to enable mclk
[  116.962475] tegra-camrtc-capture-vi tegra-capture-vi: uncorr_err: request timed out after 2500 ms
[  116.962505] tegra-camrtc-capture-vi tegra-capture-vi: err_rec: attempting to reset the capture channel
[  116.963052] tegra-camrtc-capture-vi tegra-capture-vi: err_rec: successfully reset the capture channel
[  119.522644] tegra-camrtc-capture-vi tegra-capture-vi: uncorr_err: request timed out after 2500 ms
[  119.522668] tegra-camrtc-capture-vi tegra-capture-vi: err_rec: attempting to reset the capture channel
[  119.524143] tegra-camrtc-capture-vi tegra-capture-vi: err_rec: successfully reset the capture channel
[  122.082687] tegra-camrtc-capture-vi tegra-capture-vi: uncorr_err: request timed out after 2500 ms
[  122.082714] tegra-camrtc-capture-vi tegra-capture-vi: err_rec: attempting to reset the capture channel
[  122.084142] tegra-camrtc-capture-vi tegra-capture-vi: err_rec: successfully reset the capture channel
[  124.642482] tegra-camrtc-capture-vi tegra-capture-vi: uncorr_err: request timed out after 2500 ms
[  124.642508] tegra-camrtc-capture-vi tegra-capture-vi: err_rec: attempting to reset the capture channel
[  124.643091] tegra-camrtc-capture-vi tegra-capture-vi: err_rec: successfully reset the capture channel
[  127.202701] tegra-camrtc-capture-vi tegra-capture-vi: uncorr_err: request timed out after 2500 ms
[  127.202723] tegra-camrtc-capture-vi tegra-capture-vi: err_rec: attempting to reset the capture channel
[  127.204101] tegra-camrtc-capture-vi tegra-capture-vi: err_rec: successfully reset the capture channel
[  129.762461] tegra-camrtc-capture-vi tegra-capture-vi: uncorr_err: request timed out after 2500 ms
[  129.762476] tegra-camrtc-capture-vi tegra-capture-vi: err_rec: attempting to reset the capture channel
[  129.762955] tegra-camrtc-capture-vi tegra-capture-vi: err_rec: successfully reset the capture channel
[  132.322481] tegra-camrtc-capture-vi tegra-capture-vi: uncorr_err: request timed out after 2500 ms
[  132.322507] tegra-camrtc-capture-vi tegra-capture-vi: err_rec: attempting to reset the capture channel
[  132.323031] tegra-camrtc-capture-vi tegra-capture-vi: err_rec: successfully reset the capture channel
[  134.850487] tegra-camrtc-capture-vi tegra-capture-vi: uncorr_err: request timed out after 2500 ms
[  134.850507] tegra-camrtc-capture-vi tegra-capture-vi: err_rec: attempting to reset the capture channel
[  134.851082] tegra-camrtc-capture-vi tegra-capture-vi: err_rec: successfully reset the capture channel
[  134.854840] mvcam 10-003b: camera_common_mclk_disable: no device power rail

Full Dmesg log:

Dmesg.txt

Otca

Hi,
I have successfully built the drivers for downstream/i2c on the Jetson Orin NX running Jetpack 6 (r36.3). Based on my testing, it appears that the issue is likely related to v4l2 in the upstream code, or possibly the tegra-camera.ko module.

Could you kindly provide me with the source code for v4l2 so I can attempt to build it myself? Alternatively, if possible, please share the pre-built .ko module.

Just to clarify, the board model I'm working with is the Jetson Orin NX, though v4l2 reports it as XAVIER 10-bit. I have also attached the relevant Dmesg log for your reference.

Additionally, I’ve tried both the prebuilt .ko file from your Git repository and my own built version, but both resulted in the same issue. This suggests that the problem isn’t related to the downstream/i2c modules.

Thanks in advance for your support!

Dmesg Logs

Dmesg_01.txt

v4l2-ctl --list-formats-ext
ioctl: VIDIOC_ENUM_FMT
	Type: Video Capture

	[0]: 'GREY' (8-bit Greyscale)
		Size: Discrete 1920x1080
			Interval: Discrete 0.033s (30.000 fps)
	[1]: 'XY10' (XAVIER 10-bit/16-bit Greyscale)
		Size: Discrete 1920x1080
			Interval: Discrete 0.033s (30.000 fps)
	[2]: 'XY12' (XAVIER 12-bit/16-bit Greyscale)
		Size: Discrete 1920x1080
			Interval: Discrete 0.033s (30.000 fps)

Otca

@veye_xumm
would u please give me the complete guide to build drivers needed for IMX264 on Orin NX 16GB?
For Jetpack 6.0 R36.3, I didn't find any clear instruction on the wiki.
Thanks

Otca

@veye_xumm well, I thanks you.
you helped me a lot long the pass and finally I was able to successfully work with the IMX264 on jetson Nano B01-Devkit 4GB jetpack 4.6.1 ( L4T 32.7.1).
i tested both cameras and both are Ok.
Still I have issues on other forum for Jetson Orin NX - Jetpack 6.0 (L4T 36.3).
Thanks

Otca

@veye_xumm now I have used new fresh jetpack 6.0 (R36.3) on jetson orin NX.
here is dmesg log.
I have detected camera and it has shown itself on i2c, but still I have some issues to get the video stream.

sudo dmesg| grep -i 'mvcam'
[    7.284769] mvcam 9-003b: veye mv series camera driver version: 01.01.04
[    7.786350] veye_mvcam: mvcam_read: Reading register 0x04 failed
[    7.786363] mvcam 9-003b: failed to read chip id
[    7.786367] mvcam 9-003b: mvcam_identify_module failed.
[    7.786928] mvcam 10-003b: veye mv series camera driver version: 01.01.04
[    8.288616] mvcam 10-003b: camera is: MV-MIPI-IMX264M
[    8.289601] mvcam 10-003b: firmware version: 0x1410206
[    8.295434] tegra-camrtc-capture-vi tegra-capture-vi: subdev mvcam 10-003b bound
[  354.885790] mvcam 10-003b: csi2_try format
[  354.885832] mvcam 10-003b: csi2_try format
[  354.885835] mvcam 10-003b: mvcam_csi2_get_fmt_idx_by_code success
[  354.963253] mvcam 10-003b: camera_common_mclk_enable: no device power rail
[  354.963265] mvcam 10-003b: camera_common_s_power: failed to enable mclk
[  373.489937] mvcam 10-003b: camera_common_mclk_disable: no device power rail
[  758.620283] mvcam 10-003b: csi2_try format
[  758.620326] mvcam 10-003b: csi2_try format
[  758.620332] mvcam 10-003b: mvcam_csi2_get_fmt_idx_by_code success
[  758.712221] mvcam 10-003b: camera_common_mclk_enable: no device power rail
[  758.712233] mvcam 10-003b: camera_common_s_power: failed to enable mclk
[  766.783908] mvcam 10-003b: camera_common_mclk_disable: no device power rail

Full DMESG Log:

IMX264.OrinNX.txt

i2cdetect -y -r 10
    0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:                         -- -- -- -- -- -- -- -- 
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
30: -- -- -- -- -- -- -- -- -- -- -- UU -- -- -- -- 
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
70: -- -- -- -- -- -- -- --

VLC:

I closed vlc manually after 3 seconds.

vlc
VLC media player 3.0.16 Vetinari (revision 3.0.13-8-g41878ff4f2)
[0000aaab02f4e590] main libvlc: Running vlc with the default interface. Use 'cvlc' to use vlc without interface.
[0000aaab02fee350] main playlist: playlist is empty
Opening in BLOCKING MODE
ArgusV4L2_Open failed: No such file or directory
Opening in BLOCKING MODE 
[0000ffff44001150] v4l2 demux error: cannot get streaming parameters: Inappropriate ioctl for device
[0000ffff4c000ca0] main input error: Invalid PCR value in ES_OUT_SET_(GROUP_)PCR !
[0000ffff4c000ca0] main input error: Invalid PCR value in ES_OUT_SET_(GROUP_)PCR !
[0000ffff4c000ca0] main input error: Invalid PCR value in ES_OUT_SET_(GROUP_)PCR !
[0000ffff4c000ca0] main input error: Invalid PCR value in ES_OUT_SET_(GROUP_)PCR !
[0000ffff4c000ca0] main input error: Invalid PCR value in ES_OUT_SET_(GROUP_)PCR !
[0000ffff4c000ca0] main input error: Invalid PCR value in ES_OUT_SET_(GROUP_)PCR !
[0000ffff4c000ca0] main input error: Invalid PCR value in ES_OUT_SET_(GROUP_)PCR !
[0000ffff4c000ca0] main input error: Invalid PCR value in ES_OUT_SET_(GROUP_)PCR !
Segmentation fault (core dumped)

DTB :

 cat /boot/extlinux/extlinux.conf
TIMEOUT 30
DEFAULT imx264

MENU TITLE L4T boot options

LABEL primary
      MENU LABEL primary kernel
      LINUX /boot/Image
      INITRD /boot/initrd
      APPEND ${cbootargs} root=PARTUUID=a321b5a8-b267-427e-8e1b-73b06c528581 rw rootwait rootfstype=ext4 mminit_loglevel=4 console=ttyTCU0,115200 firmware_class.path=/etc/firmware fbcon=map:0 net.ifnames=0 nospectre_bhb video=efifb:off console=tty0 nv-auto-config 


LABEL imx264
      MENU LABEL primary kernel
      LINUX /boot/Image
      FDT /boot/dtb/kernel_tegra234-p3768-0000+p3767-0000-nv.dtb
      INITRD /boot/initrd
      APPEND ${cbootargs} root=PARTUUID=a321b5a8-b267-427e-8e1b-73b06c528581 rw rootwait rootfstype=ext4 mminit_loglevel=4 console=ttyTCU0,115200 firmware_class.path=/etc/firmware fbcon=map:0 net.ifnames=0 nospectre_bhb video=efifb:off console=tty0 nv-auto-config 
      OVERLAYS /boot/dtb/tegra234-p3767-camera-p3768-veye_mvcam-dual.dtbo

ls /sys/firmware/devicetree/base/bus@0/cam_i2cmux/i2c@0/

'#address-cells'   phandle              rbpcv3_mvcam_a@3b  '#size-cells'
 name              rbpcv2_imx219_a@10   reg                 status

ls /sys/bus/i2c/drivers/

at24             dummy               max8973      pca954x             sec_pmic          vc5
axp20x-i2c       fan53555-regulator  mp8859       pf8x00              simple-mfd-i2c
bd9571mwv        fusb301             mvcam        pfuze100-regulator  smbus_alert
bq27xxx-battery  ina3221             nvvrs_pseq   rk808               tpm_i2c_infineon
cros-ec-i2c      max732x             nxp-pca9450  rohm-bd718x7        ucsi_ccg
cs2000-cp        max77620            pca953x      rtc-ds3232          usb3503

Otca

@veye_xumm indeed the camera is fine. i can refrence you to my jetson nano b01 issue.
https://forum.veye.cc/topic/634/jetson-nano-b01-mv-imx264/5

Now what should i do in order to make the jetson orin nano jetpack 6 (r36.3) works with the IMX264?
Thanks alot

Otca

@veye_xumm
thanks for your guidance.
The dmesg log is appended.
MV-MIPI-IMX264.txt

unfortunately I'm too far away from you.I'm so sorry that it's not an option for me to send board and camera.

Otca

@veye_xumm sure!
Board: Jetson Nano B01 Devkit (4GB)

uname -r

4.9.337-tegra

OS: Ubuntu 18.04.6 LTS aarch64

dpkg-query --show nvidia-l4t-core


nvidia-l4t-core 32.7.5-20240611161210

The release Version:

https://github.com/veyeimaging/nvidia_jetson_veye_bsp/releases/download/v1.29/nvidia_jetson_veye_bsp.tar.gz

DTB:

nvidia_jetson_veye_bsp/dtbs/Nano/JetPack_4.6.5_Linux_JETSON_NANO_TARGETS/dts dtb/MV-MIPI-MVCAM/tegra210-p3448-0000-p3449-0000-b00.dtb

Image:

kernel_image/Image_l4t_r32.7.5_veyecam.tar.gz

Kernel:

cat /etc/nv_tegra_release
# R32 (release), REVISION: 7.5, GCID: 36557527, BOARD: t210ref, EABI: aarch64, DATE: Tue Jun 11 23:12:44 UTC 2024

Camera

./mv_mipi_i2c.sh -r -f version -b  8

version is C 01.41 and L 02.06

Posts made by Otca