I’m having trouble with having a new IM219 module recognized on my jetson nano with the latests jetpack. I followed documentation on how to setup the drivers available in your github.
it doesn’t list in /dev/video*
I see error messages in dmsg related with arducam-csi2:
IMX219 does not have Jetvariety board and does not need to install arducam driver, you can directly connect the camera to Jetson Nano and use it.
Before that you need to uninstall the arducam driver using the following command:
sudo dpkg -r arducam-nvidia-l4t-kernel
I have Jetson nano B01 with the same system and Ardrucam IMX219-AD (B0189).
I was the same problem as @luismesas, that when I installed driver camera wasn’t recognized in dev/video*. I uninstalled this driver and camera is recognized but doesn’t work. I use command: “gst-launch-1.0 nvarguscamerasrc sensor_id=0 ! nvoverlaysink”, then computer was frozzen and restart. I used image from nvidia and from sdk then error is the same.
Tip: If the system cannot be used after running the camera, you can use the dmesg -w command to view the log in real time, and use the smartphone to take a photo and send it to us after the system crashes.
“dmesg_log_after_normal_run_up_with connect_camera.txt” Log ploted after power Nvidia Jetson and wrote dmesg -w in terminal.
“Terminal_after_gst_launch_1_0.jpg” This is picture from terminal after wrote command: “gst-launch-1.0 nvarguscamerasrc sensor_id=0 ! nvoverlaysink”. After this step Nvidia was restarted.
“dmesg_log_after_gst_launch_1_0_nvarguscamerasrc_sensor_id_0.txt” Log plot after restart Nvidia Jetson because I wrote in terminal “gst-launch-1.0 nvarguscamerasrc sensor_id=0 ! nvoverlaysink”.
I connected UART to Nvidia. I tried your command in terminal then popped up window “gst-launch-1.0” and system was frozen. Below is uart log after use this command:
Very strange phenomenon, do you have other working cameras? If you have other working imx219, it may be that the camera is damaged.
Continue to debug:
Please try this command and send us the running result and dmesg log:
v4l2-ctl --set-fmt-video=width=3264,height=2464,pixelformat=RG10 --stream-mmap --set-ctrl=sensor_mode=0 --stream-count=100 -d /dev/video0
I tried your command but it has some error, because terminal receive that: “unknown arguments: –set-fmt-video=width=3264,height=2464,pixelformat=RG10 –stream-mmap –set-ctrl=sensor_mode=0 –stream-count=100”
Thank you for the exact command. I tried to use it, then terminal didn’t show anything, but on UART was continuous show:
[ 544.267566] vi 54080000.vi: tegra_channel_error_status:error 24002 frame 0
[ 544.314819] vi 54080000.vi: tegra_channel_error_status:error 4000 frame 1
[ 544.362028] vi 54080000.vi: tegra_channel_error_status:error 4000 frame 2
[ 544.409220] vi 54080000.vi: tegra_channel_error_status:error 4000 frame 3
[ 544.456420] vi 54080000.vi: tegra_channel_error_status:error 4000 frame 4
[ 544.503624] vi 54080000.vi: tegra_channel_error_status:error 4000 frame 5
[ 544.550823] vi 54080000.vi: tegra_channel_error_status:error 4000 frame 6
[ 544.598014] vi 54080000.vi: tegra_channel_error_status:error 4000 frame 7
[ 544.645139] vi 54080000.vi: tegra_channel_error_status:error 4000 frame 8
[ 544.692426] vi 54080000.vi: tegra_channel_error_status:error 4000 frame 9
[ 544.739635] vi 54080000.vi: tegra_channel_error_status:error 4000 frame 10
.
,
.
It was displayed until used ctrl+C in Jetson terminal.