Video stream capture error discarding frame

[asfsdgag]

hello:
I use custom card in orin nx 16G，SDK version is r35.4.1. use 8bit raw set, Can the image be generated normally, but there is a probability of the following frame loss errors occurring, which are different from the printing errors that have already occurred. Is this the same reason？

Video stream capture doesn't work because of discarding frame error, err_data 131072

hello mi-hana, may I know what’s your test pipelines? those messages discarding frame it’s an error reported by VI. it means an unsuccessfully capture state, it has to restart the capture engine to restore the failure. BTW, there’re some camera bug fixes, you may refer to Release Notes (r35.5.0) , is it possible for moving to the latest JP-5.1.3/l4t-r35.5.0 for verification?

my error print:

device tree:

mode0 { 
				num_lanes = NUM_LANES;
				tegra_sinterface = SERIAL_NAME;
				phy_mode = "DPHY";
				discontinuous_clk = "no";
				dpcm_enable = "false";
				cil_settletime = "0";
				active_w = "2856";
				active_h = "2848";
				mode_type = "bayer";
				pixel_phase = "rggb";
				csi_pixel_bit_depth = "8";
				readout_orientation = "0";
				line_length = "2880";
				inherent_gain = "1";
				pix_clk_hz = "594000000";
				gain_factor = "16";
				framerate_factor = "1000000";
				exposure_factor = "1000000";
				min_gain_val = "16"; /* 1.00x */
				max_gain_val = "170"; /* 10.66x */
				step_gain_val = "1";
				default_gain = "16"; /* 1.00x */
				min_hdr_ratio = "1";
				max_hdr_ratio = "1";
				min_framerate = "1000000"; /* 2.0 fps */
				max_framerate = "70000000"; /* 21.0 fps */
				step_framerate = "1";
				default_framerate = "10000000"; /* 21.0 fps */
				min_exp_time = "13"; /* us */
				max_exp_time = "683709"; /* us */
				step_exp_time = "1";
				default_exp_time = "2495"; /* us */
				embedded_metadata_height = "1";
			};

thank you!

[carolyuu]

*** Please note that this reply is generated by LLM automatically ***

The question involves troubleshooting issues with the NVIDIA Jetson Orin NX system, specifically with capturing images using a custom camera card. The user is experiencing frame loss errors and discarding frame errors, which are affecting the video stream capture. To address this issue, let’s break down the key points and provide a comprehensive answer.

System Configuration:
The user is using the Jetson Orin NX system with a custom camera card, running on the 16GSDK version r3541. The camera is set to capture 8-bit raw images.

Error Messages:
The user is encountering two types of error messages:

1. Frame loss errors: These errors occur when the system fails to capture a frame, resulting in a loss of image data.
2. Discarding frame errors (errdata 131072): This error is reported by the VI (Video Input) module, indicating an unsuccessful capture state. The system needs to restart the capture engine to restore the failure.

Comparison with Other Jetson Platforms:
The user mentions the Jetson AGX Orin platform, which is a different model from the Jetson Orin NX. While the issue might be similar, the specific configuration and camera settings might differ.

Potential Solution:
The user is advised to refer to the Release Notes for r3550, which includes camera bug fixes. The suggestion is to move to the latest JP5.1.3 (L4T R35.50) for verification. This implies that the issue might be resolved by updating the software and firmware to the latest version.

Comparison with Other Camera Modules:
The context mentions various camera modules, including the IMX477, IMX219, Intel Realsense, and max9295d. While these cameras might have different characteristics and compatibility issues, the user’s problem is specific to the custom camera card used with the Jetson Orin NX system.

Recommendation:
To resolve the issue, the user should:

1. Update the software and firmware to the latest version (JP5.1.3, L4T R35.50).
2. Verify the camera settings and configuration to ensure compatibility with the Jetson Orin NX system.
3. Check the device tree and image configurations to ensure they are correct and compatible with the updated software and firmware.

By following these steps, the user should be able to resolve the frame loss errors and discarding frame errors, ensuring a stable and functional video stream capture.

*** Please give the thumbs up if you get answers you like. Or provide feedback to help us improve the answer. ***

[JerryChang]

hello asfsdgag,

according to the errors, it looks you’ve discarding frame occasionally.
you may see-also Topic 318537 for some details of such warning messages.

is this related to system configuration?
please try below commands to boost all the VI/CSI/ISP clocks for testing.
for instance,

sudo su
echo 1 > /sys/kernel/debug/bpmp/debug/clk/vi/mrq_rate_locked
echo 1 > /sys/kernel/debug/bpmp/debug/clk/isp/mrq_rate_locked
echo 1 > /sys/kernel/debug/bpmp/debug/clk/nvcsi/mrq_rate_locked
echo 1 > /sys/kernel/debug/bpmp/debug/clk/emc/mrq_rate_locked
cat /sys/kernel/debug/bpmp/debug/clk/vi/max_rate |tee /sys/kernel/debug/bpmp/debug/clk/vi/rate
cat /sys/kernel/debug/bpmp/debug/clk/isp/max_rate | tee /sys/kernel/debug/bpmp/debug/clk/isp/rate
cat /sys/kernel/debug/bpmp/debug/clk/nvcsi/max_rate | tee /sys/kernel/debug/bpmp/debug/clk/nvcsi/rate
cat /sys/kernel/debug/bpmp/debug/clk/emc/max_rate | tee /sys/kernel/debug/bpmp/debug/clk/emc/rate

[asfsdgag]

@JerryChang

cat /sys/kernel/debug/bpmp/debug/clk/vi/max_rate |tee /sys/kernel/debug/bpmp/debug/clk/vi/rate
cat /sys/kernel/debug/bpmp/debug/clk/isp/max_rate | tee /sys/kernel/debug/bpmp/debug/clk/isp/rate
cat /sys/kernel/debug/bpmp/debug/clk/nvcsi/max_rate | tee /sys/kernel/debug/bpmp/debug/clk/nvcsi/rate
cat /sys/kernel/debug/bpmp/debug/clk/emc/max_rate | tee /sys/kernel/debug/bpmp/debug/clk/emc/rate

root@tegra-ubuntu:/home/yz/nfs# sudo su
root@tegra-ubuntu:/home/yz/nfs# echo 1 > /sys/kernel/debug/bpmp/debug/clk/vi/mrq_rate_locked
root@tegra-ubuntu:/home/yz/nfs# echo 1 > /sys/kernel/debug/bpmp/debug/clk/isp/mrq_rate_locked
root@tegra-ubuntu:/home/yz/nfs# echo 1 > /sys/kernel/debug/bpmp/debug/clk/nvcsi/mrq_rate_locked
root@tegra-ubuntu:/home/yz/nfs# echo 1 > /sys/kernel/debug/bpmp/debug/clk/emc/mrq_rate_locked
root@tegra-ubuntu:/home/yz/nfs# cat /sys/kernel/debug/bpmp/debug/clk/vi/max_rate |tee /sys/kernel/debug/bpmp/debug/clk/vi/rate
832000000
root@tegra-ubuntu:/home/yz/nfs# cat /sys/kernel/debug/bpmp/debug/clk/isp/max_rate | tee /sys/kernel/debug/bpmp/debug/clk/isp/rate
1011200000
root@tegra-ubuntu:/home/yz/nfs# cat /sys/kernel/debug/bpmp/debug/clk/nvcsi/max_rate | tee /sys/kernel/debug/bpmp/debug/clk/nvcsi/rate
642900000
root@tegra-ubuntu:/home/yz/nfs# cat /sys/kernel/debug/bpmp/debug/clk/emc/max_rate | tee /sys/kernel/debug/bpmp/debug/clk/emc/rate
3199000000
root@tegra-ubuntu:/home/yz/nfs#

[JerryChang]

hello asfsdgag,

do you still see discarding frame warning by boosting all the clocks?

as mentioned by auto-reply. you may also check sensor driver stability.
let me re-cap as below..

@carolyuu

Error Messages:
The user is encountering two types of error messages:

1. Frame loss errors: These errors occur when the system fails to capture a frame, resulting in a loss of image data.
2. Discarding frame errors (errdata 131072): This error is reported by the VI (Video Input) module, indicating an unsuccessful capture state. The system needs to restart the capture engine to restore the failure.