Tegra-camrtc-capture-vi tegra-capture-vi: uncorr_err: request timed out after 2500 ms

[2450732921]

jetson Orin NX platform, JetPack version is Jetson Linux 36.3 (part of JetPack 6.0), the sensor will start outputting MIPI data when it is powered on (no need to configure I2C), it doesn’t support read/write of i2c, the isp used is gl3008, the sensor used is imx415, 1080p@30fps 2lane, use max9296and max9295,the pixel format is YUV422, the sensor outputs stream directly after powering on by default. The resolution of sensor is 1080p, frame rate is 30fps, pixel format is YUV422, MIPI LANE is 2, sensor outputs stream directly after power on by default, no add/drop string is used。The /dev/video0 node was successfully generated, but dmseg reported this error:
[ 162.660782] gmsl_imx415 9-0018: pcai : imx415_start_streaming
[ 165.344877] tegra-camrtc-capture-vi tegra-capture-vi: uncorr_err: request timed out after 2500 ms
[ 165.344900] tegra-camrtc-capture-vi tegra-capture-vi: err_rec: attempting to reset the capture channel
[ 165.346039] tegra-camrtc-capture-vi tegra-capture-vi: err_rec: successfully reset the capture channel
[ 167.904736] tegra-camrtc-capture-vi tegra-capture-vi: uncorr_err: request timed out after 2500 ms
[ 167.904760] tegra-camrtc-capture-vi tegra-capture-vi: err_rec: attempting to reset the capture channel
[ 167.906144] tegra-camrtc-capture-vi tegra-capture-vi: err_rec: successfully reset the capture channel
[ 170.464592] tegra-camrtc-capture-vi tegra-capture-vi: uncorr_err: request timed out after 2500 ms
[ 170.464618] tegra-camrtc-capture-vi tegra-capture-vi: err_rec: attempting to reset the capture channel
[ 170.465189] tegra-camrtc-capture-vi tegra-capture-vi: err_rec: successfully reset the capture channel
[ 173.024481] tegra-camrtc-capture-vi tegra-capture-vi: uncorr_err: request timed out after 2500 ms
[ 173.024506] tegra-camrtc-capture-vi tegra-capture-vi: err_rec: attempting to reset the capture channel
[ 173.025221] tegra-camrtc-capture-vi tegra-capture-vi: err_rec: successfully reset the capture channel
[ 175.552349] tegra-camrtc-capture-vi tegra-capture-vi: uncorr_err: request timed out after 2500 ms
[ 175.552367] tegra-camrtc-capture-vi tegra-capture-vi: err_rec: attempting to reset the capture channel
[ 175.553197] tegra-camrtc-capture-vi tegra-capture-vi: err_rec: successfully reset the capture channel
[ 175.553228] gmsl_imx415 9-0018: pcai : imx415_stop_streaming
[ 175.557905] gmsl_imx415 9-0018: imx415_power_off: power off

this is my source file:
dmesg-1516.txt (96.5 KB)
nv_gmsl_imx415.txt (27.8 KB)
tegra234-p3768-pcai-camera-gmsl-imx415.txt (48.7 KB)
tegra234-p3768-pcai-camera-gmsl-imx415-overlay.txt (7.8 KB)
trace-1516.txt (10.5 KB)

[2450732921]

Is there a problem with the DTS configuration I have set? Could you please help me take a look? I have been unable to resolve this issue, and I’m not sure what the cause is.

[ShaneCCC]

The trace log shows didn’t receive any validate data from the sensor.
You may need to probe the MIPI signal to confirm.

[2450732921]

Hi，After I made the changes, the error disappeared, but I found this new error reported, can you please tell me which configurations I should check?

max9296 9-0028: pcai : max9296_write_reg: i2c write success, 0x0051 = 0x01
 max9296 9-0028: pcai : max9296_write_reg: i2c write success, 0x0052 = 0x02
 max9296 9-0028: pcai : max9296_write_reg: i2c write success, 0x0053 = 0x03
 max9296 9-0028: pcai : various configuration according to different module
 max9296 9-0028: pcai : set all phy in ready
 max9296 9-0028: pcai : max9296_write_reg: i2c write success, 0x0332 = 0xf0
 max9296 9-0028: pcai : max9296 setup streaming - exit
 max9296 9-0028: pcai : max9296 start streaming - enter
 max9296 9-0028: pcai : max9296 start streaming - exit
 gmsl_imx415 9-0018: pcai : imx415_write_table
 max9295 9-0042: pcai : max9295d_change_port - enter
 max9295 9-0042: pcai : max9295d_change_port : ready to chang port from curr_src_csi_port : -1(0:A,1:B) to src_csi_port : 1(0:A,1:B)
 max9295 9-0042: pcai : max9295_write_reg: i2c write success, 0x02be = 0x00
 max9295 9-0042: pcai : max9295d_change_port : chang to src_csi_port : 1(0:A,1:B) success
 max9295 9-0042: pcai : max9295d_change_port - exit
 tegra-camrtc-capture-vi tegra-capture-vi: corr_err: discarding frame 0, flags: 0, err_data 131072
 tegra-camrtc-capture-vi tegra-capture-vi: corr_err: discarding frame 0, flags: 0, err_data 131072
 tegra-camrtc-capture-vi tegra-capture-vi: corr_err: discarding frame 0, flags: 0, err_data 131072
 tegra-camrtc-capture-vi tegra-capture-vi: corr_err: discarding frame 0, flags: 0, err_data 131072
 tegra-camrtc-capture-vi tegra-capture-vi: corr_err: discarding frame 0, flags: 0, err_data 131072
 tegra-camrtc-capture-vi tegra-capture-vi: corr_err: discarding frame 0, flags: 0, err_data 131072
 tegra-camrtc-capture-vi tegra-capture-vi: corr_err: discarding frame 0, flags: 0, err_data 131072
 tegra-camrtc-capture-vi tegra-capture-vi: corr_err: discarding frame 0, flags: 0, err_data 131072
 tegra-camrtc-capture-vi tegra-capture-vi: corr_err: discarding frame 0, flags: 0, err_data 131072
 tegra-camrtc-capture-vi tegra-capture-vi: corr_err: discarding frame 0, flags: 0, err_data 131072
 tegra-camrtc-capture-vi tegra-capture-vi: corr_err: discarding frame 0, flags: 0, err_data 131072
 tegra-camrtc-capture-vi tegra-capture-vi: corr_err: discarding frame 0, flags: 0, err_data 131072
 tegra-camrtc-capture-vi tegra-capture-vi: corr_err: discarding frame 0, flags: 0, err_data 131072
 tegra-camrtc-capture-vi tegra-capture-vi: corr_err: discarding frame 0, flags: 0, err_data 131072
 tegra-camrtc-capture-vi tegra-capture-vi: corr_err: discarding frame 0, flags: 0, err_data 131072
 tegra-camrtc-capture-vi tegra-capture-vi: corr_err: discarding frame 0, flags: 0, err_data 131072
 tegra-camrtc-capture-vi tegra-capture-vi: corr_err: discarding frame 0, flags: 0, err_data 131072
 tegra-camrtc-capture-vi tegra-capture-vi: corr_err: discarding frame 0, flags: 0, err_data 131072
 tegra-camrtc-capture-vi tegra-capture-vi: corr_err: discarding frame 0, flags: 0, err_data 131072

dmesg22.txt (131.0 KB)
trace22.txt (262.1 KB)

[2450732921]

Is there an error in the configuration of my device tree somewhere? Or should I check somewhere else?

[ShaneCCC]

The trace log shows the CHANSEL_SHORT_FRAME that tell the receive less lines than expected.

1. Boost the clocks to try. If help on it need to adjust the pix_clk_hz or serdes_pix_clk_hz.
2. If didn’t help it could be the sensor REG configuration problem.

[2450732921]

But currently this sensor does not need to be configured with registers, but directly out of the stream after power up, is there any other direction to verify about this error “tegra-camrtc-capture-vi tegra-capture-vi: corr_err: discarding frame 0, flags: 0, err_data 131072”? dmesg log and trace log in the previous comment

[2450732921]

this is my source file:
9295d.c.txt (37.9 KB)
9296.c.txt (50.1 KB)
imx415.c.txt (28.3 KB)
imx415.dtsi.txt (48.7 KB)
tegra234-p3768-pcai-camera-gmsl-imx415-overlay.txt (7.8 KB)

[ShaneCCC]

You can decrease the height one by one to narrow down the real output size.

[2450732921]

I tried to reduce wide to 1880 but it doesn’t grab the image properly
dmesg_1880.txt (122.3 KB)
trace_1880.txt (401.3 KB)

Also reducing the height to 1000, also boon that one comes out correctly!
dmesg_1000.txt (120.2 KB)
trace_1000.txt (392.5 KB)

can you help me ?

[2450732921]

I tried reducing wide to 1880 and it doesn’t grab the image properly
Also reducing height to 1000 does not produce a normal image

[ShaneCCC]

1880 still short frame but 1000 got pixel runaway. That tell the size in 1880 -1000 range.

[2450732921]

So may I ask how much width and height adjustment you suggest?

[ShaneCCC]

You can use binary search to figurate it.

[2450732921]

May I ask which are the valid logs? So that I know which half of the dichotomous search is valid

[ShaneCCC]

Check the detail from below link.

Jetson/l4t/Camera BringUp - eLinux.org

[2450732921]

Thanks, also, could this be a misconfiguration of the serialiser or deserialiser?

[ShaneCCC]

Maybe, you can connect directly to Jetson to confirm if possible.

[2450732921]

I have no problem connecting directly to the jeston without using the string serial/deserialiser (max9295/max9296). But after using the serial/deserialiser, it’s always ‘tegra-camrtc-capture-vi tegra-capture-vi: corr_err: discarding frame 0, flags: 0, err_data 131072’, and when I measure it with an oscilloscope, I find that the signal time difference of the deserialiser is about 29.5ms for the deserialiser and 31.3ms for the deserialiser.

[2450732921]

1. What does ‘13102’ in ‘ tegra-capture-vi: corr_err: discarding frame 0, flags: 0, err_data 131072’ mean?
2. What does ‘0x03ff200001000000’ in ‘rtcpu_vinotify_event: tstamp:3169103424 cch:0 vi:0 tag:CHANSEL_SHORT_FRAME channel:0x41 frame:0 vi_tstamp:101410554304 data. 0x03ff200001000000’ mean?
3. Can you give a very detailed explanation?