VI Gave Error "no reply from camera processor" "uncorr_err: request timed out after 2500 ms"

[f3maniramesh]

Continuing the discussion from VI shows error no reply from camera processor in xavier NX:

Hi All,
I Got the device node /dev/video0 successfully but when i try getting frames using
v4l2-ctl --set-fmt-video=width=1920,height=1080,pixelformat=UYVY --stream-mmap -d /dev/video0 --set-ctrl bypass_mode=0 --stream-count=3 --stream-to=Vid.raw

i’m getting the below Error

[ 673.581566] ev9500m 2-0010: ev9500m_power_on: power on
[ 673.666279] [RCE] vi5_hwinit: firmware CL2018101701 protocol version 2.2
[ 676.170183] tegra194-vi5 15c10000.vi: no reply from camera processor
[ 676.170339] tegra194-vi5 15c10000.vi: uncorr_err: request timed out after 2500 ms
[ 676.170504] tegra194-vi5 15c10000.vi: err_rec: attempting to reset the capture channel
[ 676.173119] tegra194-vi5 15c10000.vi: err_rec: successfully reset the capture channel
[ 678.730113] tegra194-vi5 15c10000.vi: no reply from camera processor
[ 678.730268] tegra194-vi5 15c10000.vi: uncorr_err: request timed out after 2500 ms
[ 678.730437] tegra194-vi5 15c10000.vi: err_rec: attempting to reset the capture channel
[ 678.736970] tegra194-vi5 15c10000.vi: err_rec: successfully reset the capture channel
[ 681.290037] tegra194-vi5 15c10000.vi: no reply from camera processor
[ 681.290194] tegra194-vi5 15c10000.vi: uncorr_err: request timed out after 2500 ms
[ 681.290336] tegra194-vi5 15c10000.vi: err_rec: attempting to reset the capture channel
[ 681.292113] tegra194-vi5 15c10000.vi: err_rec: successfully reset the capture channel
[ 683.817988] tegra194-vi5 15c10000.vi: no reply from camera processor
[ 683.818174] tegra194-vi5 15c10000.vi: uncorr_err: request timed out after 2500 ms
[ 683.818311] tegra194-vi5 15c10000.vi: err_rec: attempting to reset the capture channel
[ 683.820046] tegra194-vi5 15c10000.vi: err_rec: successfully reset the capture channel
[ 683.834632] ev9500m 2-0010: ev9500m_power_off: power off

Here is the trace log which i got it by following the article

Jetson/l4t/Camera BringUp - eLinux.org

cd /sys/kernel/debug/dynamic_debug/
echo file csi2_fops.c +p > control

control (665.1 KB)

[ShaneCCC]

That’s no trace log.

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 2 > /sys/kernel/debug/camrtc/log-level
echo 1 > /sys/kernel/debug/tracing/events/camera_common/enable
echo > /sys/kernel/debug/tracing/trace

Run the command to capture.

cat /sys/kernel/debug/tracing/trace

[f3maniramesh]

@ShaneCCC

Yeah, I got it now.
Here is the Trace log

camTraceLog (59.8 KB)

[ShaneCCC]

Looks like didn’t receive any validate data from sensor.
I would suggest probe the MIPI signal to confirm it.

Thanks

[f3maniramesh]

I’m Sorry @ShaneCCC
I have only CRO btw ill be able to check the clock signal

Are you sure about it ? why because we have tested with other camera also but got the same response

[f3maniramesh]

I Probed the MIPI Signals and i’m getting signals

[JerryChang]

hello f3maniramesh,

the device tree port binding should be correct since you’ve camera device register to linux kernel.
could you please double check your signal property configure in device tree settings.
furthermore, you may also try to boost up the clock to max for checking.
for example,

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
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