Xavier can not received MIPI signal

Hi everyone,

I’m using Xavier to capture raw image.
Image information:

  • DPHY x 4lane
  • resolution: 5940x4418
  • image bit depth:12

First step, we simulate the MIPI signal in the lab. Then Xavier success received the data.
Second step, we use real camera to capture image. But Xavier can not start to received.

The Xavier setting is the same.

According other discuss link I try to trace the kernel by type commands.

sudo echo 1 > /sys/kernel/debug/tracing/tracing_on
sudo echo 30720 > /sys/kernel/debug/tracing/buffer_size_kb
sudo echo 1 > /sys/kernel/debug/tracing/events/tegra_rtcpu/enable
sudo echo 1 > /sys/kernel/debug/tracing/events/freertos/enable
sudo echo 2 > /sys/kernel/debug/camrtc/log-level
sudo echo 1 > /sys/kernel/debug/tracing/events/camera_common/enable
sudo echo > /sys/kernel/debug/tracing/trace
cat /sys/kernel/debug/tracing/trace

Below is log

kworker/0:3-2151 [000] … 630.005940: rtos_queue_peek_from_isr_failed: tstamp:20144931648 queue:0x0bcbb8b8
kworker/0:3-2151 [000] … 630.173936: rtos_queue_peek_from_isr_failed: tstamp:20149931648 queue:0x0bcbb8b8
kworker/0:3-2151 [000] … 630.341925: rtos_queue_peek_from_isr_failed: tstamp:20154931651 queue:0x0bcbb8b8
kworker/0:3-2151 [000] … 630.509938: rtos_queue_peek_from_isr_failed: tstamp:20159931655 queue:0x0bcbb8b8
kworker/0:3-2151 [000] … 630.677923: rtos_queue_peek_from_isr_failed: tstamp:20164931652 queue:0x0bcbb8b8

1226trace.txt (39.3 KB)

What does it mean rtos_queue_peek_from_isr_failed: tstamp:20159931655 queue:0x0bcbb8b8?
And How can I get those error msg mean in Xavier TRM?

Thanks a lot.
syan

hello syan,

could you please start with CSI data rate calculation, you should also consider 15% protocol overhead.
for example,
CSI data rate = image width * image height * frame-rate * bits per pixel * 1.15

Hi @JerryChang,

The dmesg shows as below,


It seem to start received?

But I still can’t capture image…

hello syan,

the error message… no reply from camera processor, it means there’s no camera frames detected by VI engine.
please evaluate CSI data rate, moreover, may I know which JetPack release you’re using?
please see-also SerDes Pixel Clock session,
that’s r35.1 added feature for waiting skew calibration if the sensor output data rate is > 1.5Gbps…

Hi @JerryChang

We use oscilloscope to check, it’s 300Mbps

JetPack version: 32.7.1
image

thanks.
syan

Boost clocks to try.

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

Hi @ShaneCCC ,

Step as below?

Step 1.)

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

Step 2.)
try to capture.

Step 3.)

sudo echo 1 > /sys/kernel/debug/tracing/tracing_on
sudo echo 30720 > /sys/kernel/debug/tracing/buffer_size_kb
sudo echo 1 > /sys/kernel/debug/tracing/events/tegra_rtcpu/enable
sudo echo 1 > /sys/kernel/debug/tracing/events/freertos/enable
sudo echo 2 > /sys/kernel/debug/camrtc/log-level
sudo echo 1 > /sys/kernel/debug/tracing/events/camera_common/enable
sudo echo > /sys/kernel/debug/tracing/trace
cat /sys/kernel/debug/tracing/trace

Does It right?

thanks.
syan

Exchange step 2/3 and get the trace log by below after capture command.

cat /sys/kernel/debug/tracing/trace

Hi @ShaneCCC ,
thanks your reply.

Here’s trace log.
1227.txt (77.6 KB)
1227_dmesg.txt (75.9 KB)

It shows

kworker/0:1-723 [000] … 357.519755: rtos_queue_peek_from_isr_failed: tstamp:11628258781 queue:0x0bcbb8b8
kworker/0:1-723 [000] … 357.631744: rtos_queue_peek_from_isr_failed: tstamp:11633258779 queue:0x0bcbb8b8
kworker/0:1-723 [000] … 357.799745: rtos_queue_peek_from_isr_failed: tstamp:11638258779 queue:0x0bcbb8b8
kworker/0:1-723 [000] … 357.967739: rtos_queue_peek_from_isr_failed: tstamp:11643258779 queue:0x0bcbb8b8
kworker/0:1-723 [000] … 358.135752: rtos_queue_peek_from_isr_failed: tstamp:11648258779 queue:0x0bcbb8b8
kworker/0:1-723 [000] … 358.303761: rtos_queue_peek_from_isr_failed: tstamp:11653258779 queue:0x0bcbb8b8
kworker/0:1-723 [000] … 358.471781: rtos_queue_peek_from_isr_failed: tstamp:11658258777 queue:0x0bcbb8b8

What does it mean?

thanks.
syan

You can just ignore those message.
From your trace log NVCSI/VI didn’t receive any validate data as Jerry’s comment.
You may need confirm the port-index and probe the signal is match MIPI spec.
Also you can try configure the sensor output discontinuous clocks to try.

Hi @ShaneCCC ,
Jerry’s comment to adjust Device Tree file parameter pix_clk_hz

In my case, it will be = 5940 * 4418 * 3.5 * 12 * 1.15 = 1,267,533,036‬
I set it 1600,000,000

But When I flash Xavier, it can not find /dev/video0
And dmesg shows

46B9D0E8F0D1A15924690FE740E7354A2BDBF572

Only change this parameter just got error…

BTW,

Do you mean DT file discontinuous_clk = “yes”; ?
I had setted that.

thanks
syan

I don’t think modify the pix_clk_hz would cause this issue.
Suppose you can modify it back due to r32 release don’t have the 1.5Gbpps limitation.

Yes but need to modify the sensor output as discontinuous mode to match this configure.

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