NVidia Jetson Jetpack 6 support?
-
@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 fpsAccording 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 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 -
Ok, I have the same mvcam imx296m with adp-mv1 adapter connected to Orin nx 16GB board from seeed studio.
I used overlay dtbo loading method. The ‘sudo insmod veye_mvcam.ko’ ran w/o error returning.
But I got these errors checking ‘dmesg| grep -i mvcam’:
What could be the reason? I tried both local build .ko and downloaded (latest version) .ko files. Same symptom.
My system is R36.3 Jetpack 6.0.
BTW, where does the tegra_camera.ko come from? I seem do not find place to compile it. Thanks.
-
Also, besides the tegra-camera.ko question, I noticed the v4l2-core/*.ko also different between nvidia_jetson_veye_bsp release tar ball and default *.ko in /lib/modules/$(uname -r)/kernel/drivers/media/v4l2-core/. How are these *.ko files are compiled in nvidia_jetson_veye_bsp.tar.gz and where are the source files?
sudo cp nvidia_jetson_veye_bsp/ko/$(uname -r)/upstream/*.ko /lib/modules/$(uname -r)/kernel/drivers/media/v4l2-core/ -f -
@vitob
I think the first thing you need to check is whether this baseboard from seed is compatible with the official nVidia carrier board and whether it uses the same dtb？ -
@vitob Pls try to get version:
https://wiki.veye.cc/index.php/Mv_mipi_i2c.sh_user_guide#model -
nvidia@ubuntu:/work/git_repo/nvidia_jetson_veye_bsp/mv_tools_jetson/i2c_tools$ ./mv_mipi_i2c.sh -r -f model -b 0
model 0 not recognized
nvidia@ubuntu:/work/git_repo/nvidia_jetson_veye_bsp/mv_tools_jetson/i2c_tools$ ./mv_mipi_i2c.sh -r -f model -b 1
model 0 not recognized
nvidia@ubuntu:/work/git_repo/nvidia_jetson_veye_bsp/mv_tools_jetson/i2c_tools$ ./mv_mipi_i2c_new.sh -r -f model -b 1
NOT SUPPORTED!
nvidia@ubuntu:/work/git_repo/nvidia_jetson_veye_bsp/mv_tools_jetson/i2c_tools$ ./mv_mipi_i2c_new.sh -r -f model -b 0
NOT SUPPORTED! -
@veye_xumm , let me confirm this, although I used sdkmanager to flash the board with nvidia native packages w/o issues.
-
@vitob said in NVidia Jetson Jetpack 6 support?:
tegra-camera.ko question, I noticed the v4l2-core/*.ko
In the meantime, can you help explain this question on tegra-camera.ko and v4l2-core/*.ko? Why they needs to be updated and where can I find the source code of them? Once updating them using the veye release .ko, will that affect other cameras (for example, I want to port/develop driver for another sensor myself)? Thanks.
-
@vitob
Please use -b 9 or -b 10 as an argument.https://wiki.veye.cc/index.php/I2c_bus_number_and_video_node
For i2c bus number, please refer to this link above.
-
@vitob said in NVidia Jetson Jetpack 6 support?:
In the meantime, can you help explain this question on tegra-camera.ko and v4l2-core/*.ko? Why they needs to be updated and where can I find the source code of them? Once updating them using the veye release .ko, will that affect other cameras (for example, I want to port/develop driver for another sensor myself)? Thanks.
These driver changes add support for RAW8 RAW10 RAW12 data types on the one hand, and externally triggered modes on the other.
Their code reference:
https://github.com/veyeimaging/nvidia_jetson_veye_bsp/tree/master/kernel_patch_4_mv/l4t-r36.3Compile step by step reference:：
https://wiki.veye.cc/index.php/VEYE_CS_Camera_source_for_Jetson
