spavan
November 22, 2024, 6:35am
1
Hi @ShaneCCC
I have IMX334(4 lane) connected to my Serdes setup with GMSL protocol , I could see the below error for the below command ,after boosting the clocks as well
v4l2-ctl -d /dev/video0 --set-ctrl bypass_mode=0 --stream-mmap --stream-count=100
[ 195.807587] tegra-camrtc-capture-vi tegra-capture-vi: uncorr_err: request timed out after 2500 ms
[ 195.808492] tegra-camrtc-capture-vi tegra-capture-vi: err_rec: attempting to reset the capture channel
[ 195.809675] (NULL device *): vi_capture_control_message: NULL VI channel received
[ 195.809872] t194-nvcsi 13e10000.host1x:nvcsi@15a00000: csi5_stream_close: Error in closing stream_id=0, csi_port=0
[ 195.810092] (NULL device *): vi_capture_control_message: NULL VI channel received
[ 195.810263] t194-nvcsi 13e10000.host1x:nvcsi@15a00000: csi5_stream_open: VI channel not found for stream- 0 vc- 0
[ 195.811011] tegra-camrtc-capture-vi tegra-capture-vi: err_rec: successfully reset the capture channel
[ 198.335649] tegra-camrtc-capture-vi tegra-capture-vi: uncorr_err: request timed out after 2500 ms
[ 198.335911] tegra-camrtc-capture-vi tegra-capture-vi: err_rec: attempting to reset the capture channel
[ 198.336596] (NULL device *): vi_capture_control_message: NULL VI channel received
[ 198.336779] t194-nvcsi 13e10000.host1x:nvcsi@15a00000: csi5_stream_close: Error in closing stream_id=0, csi_port=0
[ 198.337003] (NULL device *): vi_capture_control_message: NULL VI channel received
[ 198.337174] t194-nvcsi 13e10000.host1x:nvcsi@15a00000: csi5_stream_open: VI channel not found for stream- 0 vc- 0
[ 198.337793] tegra-camrtc-capture-vi tegra-capture-vi: err_rec: successfully reset the capture channel
spavan
November 22, 2024, 6:50am
3
mode1 {/*IMX334_MODE_1920x1080*/
mclk_khz = "24000";
num_lanes = "4";
tegra_sinterface = "serial_a";
discontinuous_clk = "yes";
dpcm_enable = "false";
cil_settletime = "0";
dynamic_pixel_bit_depth = "12";
csi_pixel_bit_depth = "12";
mode_type = "bayer";
pixel_phase = "rggb";
active_w = "1944";
active_h = "1090";
readout_orientation = "0";
line_length = "5500";
inherent_gain = "1";
mclk_multiplier = "30";
pix_clk_hz = "712800000";
gain_factor = "1";
framerate_factor = "1000000";
exposure_factor = "1000000";
min_gain_val = "1"; /* 1 dB */
max_gain_val = "72"; /* 72 dB */
step_gain_val = "1";
default_gain = "1";
min_hdr_ratio = "1";
max_hdr_ratio = "1";
min_framerate = "1000000"; /* 1.0 fps */
max_framerate = "60000000"; /* 60.0 fps */
step_framerate = "1";
default_framerate = "60000000"; /* 60.0 fps */
min_exp_time = "13"; /* us */
max_exp_time = "16638"; /* us */
step_exp_time = "1";
default_exp_time = "2495"; /* us */
embedded_metadata_height = "1";//made changes from working 1->0 for testing
};
ports {
#address-cells = <1>;
#size-cells = <0>;
port@0 {
reg = <0>;
liimx334_imx334_out0: endpoint {
port-index = <0>;
bus-width = <4>;
remote-endpoint = <&liimx334_imx334_csi_in0>;
};
};
};
};
};
ioctl: VIDIOC_ENUM_FMT
Type: Video Capture
[0]: 'RG12' (12-bit Bayer RGRG/GBGB)
Size: Discrete 1920x1080
Interval: Discrete 0.017s (60.000 fps)
Package: nvidia-jetpack
Version: 5.1.2-b104
Architecture: arm64
Maintainer: NVIDIA Corporation
Installed-Size: 194
Depends: nvidia-jetpack-runtime (= 5.1.2-b104), nvidia-jetpack-dev (= 5.1.2-b104)
Homepage: http://developer.nvidia.com/jetson
Priority: standard
Section: metapackages
Filename: pool/main/n/nvidia-jetpack/nvidia-jetpack_5.1.2-b104_arm64.deb
Size: 29304
SHA256: fda2eed24747319ccd9fee9a8548c0e5dd52812363877ebe90e223b5a6e7e827
SHA1: 78c7d9e02490f96f8fbd5a091c8bef280b03ae84
MD5sum: 6be522b5542ab2af5dcf62837b34a5f0
Description: NVIDIA Jetpack Meta Package
Description-md5: ad1462289bdbc54909ae109d1d32c0a8
L4T 35.4.1 version
vi-output, imx3-3029 [001] .... 3152.567667: tegra_channel_capture_setup: vnc_id 0 W 1920 H 1080 fmt c4
kworker/3:8-202 [003] .... 3152.621405: rtcpu_vinotify_event: tstamp:99278308473 cch:0 vi:0 tag:VIFALC_TDSTATE channel:0x23 frame:0 vi_tstamp:3176905757856 data:0xcd9ce50010000000
kworker/3:8-202 [003] .... 3152.621409: rtcpu_vinotify_event: tstamp:99278308632 cch:0 vi:0 tag:VIFALC_TDSTATE channel:0x23 frame:0 vi_tstamp:3176905769632 data:0x0000000031000001
kworker/3:8-202 [003] .... 3152.621410: rtcpu_vinotify_event: tstamp:99278308796 cch:0 vi:0 tag:VIFALC_TDSTATE channel:0x23 frame:0 vi_tstamp:3176905824736 data:0xcd9ce20010000000
kworker/3:8-202 [003] .... 3152.621411: rtcpu_vinotify_event: tstamp:99278308937 cch:0 vi:0 tag:VIFALC_TDSTATE channel:0x23 frame:0 vi_tstamp:3176905836672 data:0x0000000031000002
Get the trace logt.
sudo su
echo 1 > /sys/kernel/debug/tracing/tracing_on
echo 30720 > /sys/kernel/debug/tracing/buffer_size_kb
echo 1 > /sys/kernel/debug/tracing/events/tegra_rtcpu/enable
echo 1 > /sys/kernel/debug/tracing/events/freertos/enable
echo 3 > /sys/kernel/debug/camrtc/log-level
echo 1 > /sys/kernel/debug/tracing/events/camera_common/enable
echo > /sys/kernel/debug/tracing/trace
v4l2-ctl --stream-mmap -c bypass_mode=0
cat /sys/kernel/debug/tracing/trace
spavan
November 22, 2024, 8:24am
5
The trace log shows didn’t receive any validate data from the sensor.
You may need to probe the MIPI signal to confirm.
spavan
November 25, 2024, 4:25am
7
ok @ShaneCCC , we will get back to you after probing.
spavan
November 25, 2024, 4:48am
8
but it is working when directly connected to the Xavier , this errors are received only during Serdes setup
Then checking the Serdes configuration. And the signal from the Serdes to XNX.
spavan
November 26, 2024, 5:04am
10
hi @ShaneCCC
I could see the packets from the camera , but after sometime i could see the CANCELLED error as shown in the attached log.
camera_error.txt (807 Bytes)
Please check with serdes vendor. I don’t think argus work if v4l2-ctl can’t capture from the MIPI bus.
spavan
November 26, 2024, 5:28am
12
it is capturing , but the packets are getting dropped after certain time and I have 2.04 Gbps for 4 lane camera
what exactly the attached error mean ?
I can’t tell what by the error. Do you make sure v4l2-ctl working?
spavan
November 26, 2024, 5:33am
14
kworker/1:4-146 [001] .... 2935.493378: rtcpu_vinotify_event: tstamp:92488564275 cch:0 vi:0 tag:VIFALC_TDSTATE channel:0x23 frame:0 vi_tstamp:2959633533696 data:0xcd9ce50010000000
kworker/1:4-146 [001] .... 2935.493382: rtcpu_vinotify_event: tstamp:92488564446 cch:0 vi:0 tag:VIFALC_TDSTATE channel:0x23 frame:0 vi_tstamp:2959633577056 data:0x0000000031000001
kworker/1:4-146 [001] .... 2935.493383: rtcpu_vinotify_event: tstamp:92488564621 cch:0 vi:0 tag:VIFALC_TDSTATE channel:0x23 frame:0 vi_tstamp:2959633595680 data:0xcd9ce20010000000
kworker/1:4-146 [001] .... 2935.493384: rtcpu_vinotify_event: tstamp:92488564772 cch:0 vi:0 tag:VIFALC_TDSTATE channel:0x23 frame:0 vi_tstamp:2959633656704 data:0x0000000031000002
[ 2152.562692] tegradc 15210000.display: blank - powerdown
[ 2932.909491] tegra-camrtc-capture-vi tegra-capture-vi: uncorr_err: request timed out after 2500 ms
[ 2932.909934] tegra-camrtc-capture-vi tegra-capture-vi: err_rec: attempting to reset the capture channel
[ 2932.911034] (NULL device *): vi_capture_control_message: NULL VI channel received
[ 2932.911262] t194-nvcsi 13e10000.host1x:nvcsi@15a00000: csi5_stream_close: Error in closing stream_id=2, csi_port=2
[ 2932.911456] (NULL device *): vi_capture_control_message: NULL VI channel received
[ 2932.911602] t194-nvcsi 13e10000.host1x:nvcsi@15a00000: csi5_stream_open: VI channel not found for stream- 2 vc- 0
i am receiving these errors for v4l2-ctl
This tell the output signal have problem to receive data from the sensor.
You need to check the HW signal first.
spavan
November 26, 2024, 5:47am
16
v4l2-ctl --stream-mmap -c bypass_mode=0
what this command is trying to do in the serdes setup?
spavan
December 3, 2024, 9:21am
18
HI @ShaneCCC ,
Now i can receive the data at both the ends serializer and deserializer but only for few secs with black window , and trace error as below
kworker/1:4-146 [001] .... 2935.493378: rtcpu_vinotify_event: tstamp:92488564275 cch:0 vi:0 tag:VIFALC_TDSTATE channel:0x23 frame:0 vi_tstamp:2959633533696 data:0xcd9ce50010000000 kworker/1:4-146 [001] .... 2935.493382: rtcpu_vinotify_event: tstamp:92488564446 cch:0 vi:0 tag:VIFALC_TDSTATE channel:0x23 frame:0 vi_tstamp:2959633577056 data:0x0000000031000001 kworker/1:4-146 [001] .... 2935.493383: rtcpu_vinotify_event: tstamp:92488564621 cch:0 vi:0 tag:VIFALC_TDSTATE channel:0x23 frame:0 vi_tstamp:2959633595680 data:0xcd9ce20010000000 kworker/1:4-146 [001] .... 2935.493384: rtcpu_vinotify_event: tstamp:92488564772 cch:0 vi:0 tag:VIFALC_TDSTATE channel:0x23 frame:0 vi_tstamp:2959633656704 data:0x0000000031000002
spavan
December 3, 2024, 11:31am
19
hi @ShaneCCC ,
can this be possible due to i2c configurations also?
For example: the speed of i2c
Looks like still didn’t receive any validate data from the sensor.
You can check the kernel message to confirm if any i2c failed.
spavan
December 5, 2024, 4:40am
21
No i2c errors from dmesg logs
And now i could not see the below error what does it mean?
[ 2152.562692] tegradc 15210000.display: blank - powerdown
[ 2932.909491] tegra-camrtc-capture-vi tegra-capture-vi: uncorr_err: request timed out after 2500 ms
[ 2932.909934] tegra-camrtc-capture-vi tegra-capture-vi: err_rec: attempting to reset the capture channel
[ 2932.911034] (NULL device *): vi_capture_control_message: NULL VI channel received
[ 2932.911262] t194-nvcsi 13e10000.host1x:nvcsi@15a00000: csi5_stream_close: Error in closing stream_id=2, csi_port=2
[ 2932.911456] (NULL device *): vi_capture_control_message: NULL VI channel received
[ 2932.911602] t194-nvcsi 13e10000.host1x:nvcsi@15a00000: csi5_stream_open: VI channel not found for stream- 2 vc- 0