Issue: capturing frames from IMX296 camera sensor on Nvidia Jetson Orin Nano

Hello Nvidia community,

I’m working on a project with the NVIDIA Jetson Orin Nano, and I’m using it with a camera sensor IMX296. I am able to probe the driver of the sensor, but I’m running into issues when trying to capture a frame.
Any guidance on how to resolve this issue or steps for further troubleshooting would be greatly appreciated.

The following errors are being logged:

Nano:~/latest_modules$v4l2-ctl -d 0 --set-fmt-video=width=728,height=544 --stream-mmap --stream-count=100000 -c preferred_stride=1472 -c override_enable=1,gain=0,frame_rate=120,exposure=1000000 -c sensor_mode=0
[ 4441.588712] bwmgr API not supported
[ 4444.290559] tegra-camrtc-capture-vi tegra-capture-vi: uncorr_err: request timed out after 2500 ms
[ 4444.290777] tegra-camrtc-capture-vi tegra-capture-vi: err_rec: attempting to reset the capture channel
[ 4444.292202] (NULL device *): vi_capture_control_message: NULL VI channel received
[ 4444.292371] t194-nvcsi 13e40000.host1x:nvcsi@15a00000: csi5_stream_close: Error in closing stream_id=2, csi_port=2
[ 4444.292601] (NULL device *): vi_capture_control_message: NULL VI channel received
[ 4444.292770] t194-nvcsi 13e40000.host1x:nvcsi@15a00000: csi5_stream_open: VI channel not found for stream- 2 vc- 0
[ 4444.293266] tegra-camrtc-capture-vi tegra-capture-vi: err_rec: successfully reset the capture channel
[ 4446.850438] tegra-camrtc-capture-vi tegra-capture-vi: uncorr_err: request timed out after 2500 ms
[ 4446.850671] tegra-camrtc-capture-vi tegra-capture-vi: err_rec: attempting to reset the capture channel
[ 4446.852174] (NULL device *): vi_capture_control_message: NULL VI channel received
[ 4446.852349] t194-nvcsi 13e40000.host1x:nvcsi@15a00000: csi5_stream_close: Error in closing stream_id=2, csi_port=2
[ 4446.852587] (NULL device *): vi_capture_control_message: NULL VI channel received
[ 4446.852754] t194-nvcsi 13e40000.host1x:nvcsi@15a00000: csi5_stream_open: VI channel not found for stream- 2 vc- 0
[ 4446.853267] tegra-camrtc-capture-vi tegra-capture-vi: err_rec: successfully reset the capture channel

hello kavandhamsania,

the error log… NULL VI channel received usually caused by an incorrect port bindings.
please refer to Port Binding section to examine your port binding for VI (video input), NvCSI, and sensor modules.
you should also enter the command, $ sudo media-ctl -p -d /dev/media0 to verify the port binding result.

BTW,
may I know which Jetpack release version you’re working with?
if that’s possible, please try moving forward to the latest release for confirmation.

Hello Nvidia community,

Thank you for your response and suggestions. I have followed your advice and checked the port binding for VI, NvCSI, and the sensor modules using the command “$ sudo media-ctl -p -d /dev/media0.” I have attached the Screen Shot.

I want to confirm that I have supplied the voltage externally to the imx296 sensor instead of using Jetson’s regulator supply. Additionally, I have set the MCLK to 37.125MHz in accordance with the guidelines provided in the datasheet.

Considering the information provided, could you please provide any further insights or guidance on how to resolve the issue I am experiencing with capturing frames from the IMX296 sensor?

Thank you again for your continued support.

hello kavandhamsania,

according to that port binding results, I assume you’ve device node (i.e. /dev/video0) register to linux kernel, right?
please check developer guide, Applications Using V4L2 IOCTL Directly. please use V4L2 IOCTL to verify basic camera functionality.

you may dump the sensor capability with… $ v4l2-ctl -d /dev/video0 --list-formats-ext
here’s a sample command line to fetch sensor stream,
please do update those width/height/format parameters with your sensor supported formats accordingly.
for instance,
$ v4l2-ctl -d /dev/video0 --set-fmt-video=width=1920,height=1080,pixelformat=RG10 --set-ctrl bypass_mode=0 --stream-mmap --stream-count=100

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.