veyeimaging / nvidia_jetson_veye_bsp Goto Github PK

Looking at the latest release and it appears that the signed_4_xavier file is missing for both r32.7.3 and r32.7.4.

...
Image_l4t_r32.6.1_veyecam_signed_4_xavier.tgz
Image_l4t_r32.6.1_veyecam.tar.gz
Image_l4t_r32.7.1_veyecam_signed_4_xavier.tgz
Image_l4t_r32.7.1_veyecam.tar.gz
Image_l4t_r32.7.3_veyecam_signed_4_xavier.tgz <-- MISSING
Image_l4t_r32.7.3_veyecam.tar.gz
Image_l4t_r32.7.4_veyecam_signed_4_xavier.tgz <-- MISSING
Image_l4t_r32.7.4_veyecam.tar.gz
Image_l4t_r35.1_mvcam_patched_signed_4_xavier_orin.tgz
...

使用v4l2gray_mvcam_jetson工具时出现反馈信息

之后将v4l2代码中尺寸设置为2496x2056时图像正常显示。之后再次测试重启设备后直接捕获2496x2056的图像出现错行读取数据长度为5065984（2464x2056）,再次调用v4l2gray_mvcam_jetson后，运行v4l2代码捕获图像正常。长度为

期望：能够正常运行v4l2代码捕获2496x2056尺寸图像。

Hi, I've bought a MV-MIPI-IMX296M module. From documentation, it seems all examples are based on V4l2 driver stack. Does it support going through NVidia Jetson built-in ISP hw and Argus pipeline? Thanks.

这样就可以不用和内核一起编译，降低时间成本。

Hi developers,

I stuck at the Build Kernel step since I miss the kernel_csimx307veye327_config_32.4.2 in drivers_source. In this case, I am wondering is it possible to use kernel_csimx307veye327_config_r32.3.1 for R32.4.2 version. Or, can you provide the missed file?

Hi, I have updated image、ko and dbt files through prebuilt binaries as the wiki. After all the done, I checked if the update was successful:

I can find the csx307 of the output of ls /sys/bus/i2c/drivers/, but there is no any "307" of the output of ls /proc/device-tree/cam_i2cmux/i2c@*.

My board is Xavier NX and the system is Jetpack 5.0.2, I have double checked the dbt files and extlinux.conf. Could you give any suggestions?