Orin jetpack5.1.2 When the data rate of each channel is 1.8Gbps, Csi2 cannot receive frames

Robotics & Edge Computing Jetson Systems Jetson AGX Orin
23

hello 305248199,

you did not get my point, as mentioned in previous comment #17, the main problem here is no frame packets has received by VI engine.

please following the formula… Output data rate = (sensor or deserializer pixel clock in hertz) * (bits per pixel) / (number of CSI lanes)
and… please configure a higher (15% or more) data-rate to serdes pixel clock for testing.

24

I have tried all the following parameters, but they are not working,

企业微信截图_17198019572412

25

hello 305248199,

did you confirm you’ve update DT property correctly?
here’s an example to examine pixel clock on the target…
$ sudo cat /proc/device-tree/i2c@3180000/tca9548@77/i2c@0/ov5693_a@36/mode0/pix_clk_hz

26

The camera supplier said that the PCLK is 74250000
So, pix_clk_hz=“74250000”;

27

I have also tried pix_clk_hz=“88473600”;
Same phenomenon

28

hello 305248199,

you should configure serdes_pix_clk_hz, which should be larger than pix_clk_hz.
may I also know what’s your steps for device tree property update, please check on target directly to ensure you’ve update the value accordingly.

29

There are many values that have been tried, and the values obtained from the calculation are tested by taking upper and lower values
They all have a value of ‘serdes_pix_clk_hz’ greater than ‘pix_clk_hz’

30

did you checked and confirmed on target directly to ensure you’ve update the value accordingly.

31

yes , we have

32

root@ubuntu:/home/cookoo# cat /proc/device-tree/i2c@3180000/ar0234b_a@11/mode0/pix_clk_hz
74250000root@ubuntu:/home/cookoo# cat /proc/device-tree/i2c@3180000/ar0234b_a@11/mode0/serdes_pix_clk_hz
355555555root@ubuntu:/home/cookoo#

33

Currently, this configuration is undergoing testing

34

May I ask what the camera trace log below means? How to solve it?

tracer: nop

entries-in-buffer/entries-written: 15280/15280 #P:8

_-----=> irqs-off

/ _----=> need-resched

| / _—=> hardirq/softirq

|| / _–=> preempt-depth

||| / delay

TASK-PID CPU# |||| TIMESTAMP FUNCTION

| | | |||| | |

kworker/0:15-202     [000] ....    91.814534: rtcpu_string: tstamp:3470984845 id:0x04010000 str:"VM0 deactivating."
kworker/0:15-202     [000] ....    99.950537: rtcpu_string: tstamp:3724701575 id:0x04010000 str:"VM0 activating."
kworker/0:15-202     [000] ....   100.178549: rtcpu_isp_falcon_task_start: tstamp:3732793633 ch:0 task:HANDLE_EVENT
kworker/0:15-202     [000] ....   100.178556: rtcpu_isp_falcon_task_end: tstamp:3732793673 task:HANDLE_EVENT
kworker/0:15-202     [000] ....   100.934574: rtcpu_vinotify_event: tstamp:3755775141 cch:0 vi:0 tag:VIFALC_TDSTATE channel:0x23 frame:0 vi_tstamp:120168463040 data:0x359d580010000000
kworker/0:15-202     [000] ....   100.934578: rtcpu_vinotify_event: tstamp:3755775277 cch:0 vi:0 tag:VIFALC_TDSTATE channel:0x23 frame:0 vi_tstamp:120168469536 data:0x0000000031000001
kworker/0:15-202     [000] ....   100.934578: rtcpu_vinotify_event: tstamp:3755775431 cch:0 vi:0 tag:VIFALC_TDSTATE channel:0x23 frame:0 vi_tstamp:120168530240 data:0x359d550010000000
kworker/0:15-202     [000] ....   100.934579: rtcpu_vinotify_event: tstamp:3755775562 cch:0 vi:0 tag:VIFALC_TDSTATE channel:0x23 frame:0 vi_tstamp:120168536832 data:0x0000000031000002
kworker/0:15-202     [000] ....   100.934581: rtcpu_nvcsi_intr: tstamp:3755820553 class:GLOBAL type:STREAM_VC phy:0 cil:0 st:0 vc:0 status:0x00000008
kworker/0:15-202     [000] ....   100.934582: rtcpu_nvcsi_intr: tstamp:3755820553 class:CORRECTABLE_ERR type:STREAM_VC phy:0 cil:0 st:0 vc:0 status:0x00000008
kworker/0:15-202     [000] ....   100.934582: rtcpu_nvcsi_intr: tstamp:3755821737 class:GLOBAL type:STREAM_VC phy:0 cil:0 st:0 vc:0 status:0x00000004
kworker/0:15-202     [000] ....   100.934583: rtcpu_nvcsi_intr: tstamp:3755821737 class:CORRECTABLE_ERR type:STREAM_VC phy:0 cil:0 st:0 vc:0 status:0x00000004
kworker/0:15-202     [000] ....   100.934584: rtcpu_vinotify_error: tstamp:3755823629 cch:-1 vi:0 tag:CSIMUX_STREAM channel:0x00 frame:0 vi_tstamp:120186251680 data:0x0000000000000001
kworker/0:15-202     [000] ....   100.934585: rtcpu_nvcsi_intr: tstamp:3755828162 class:GLOBAL type:STREAM_VC phy:0 cil:0 st:0 vc:1 status:0x00000004
kworker/0:15-202     [000] ....   100.934585: rtcpu_nvcsi_intr: tstamp:3755828162 class:CORRECTABLE_ERR type:STREAM_VC phy:0 cil:0 st:0 vc:1 status:0x00000004
kworker/0:15-202     [000] ....   100.934586: rtcpu_vinotify_error: tstamp:3755830057 cch:-1 vi:0 tag:CSIMUX_STREAM channel:0x00 frame:1 vi_tstamp:120186465728 data:0x0000000000000001
kworker/0:15-202     [000] ....   100.934587: rtcpu_nvcsi_intr: tstamp:3755870446 class:GLOBAL type:STREAM_VC phy:0 cil:0 st:0 vc:1 status:0x00000004
kworker/0:15-202     [000] ....   100.934587: rtcpu_nvcsi_intr: tstamp:3755870446 class:CORRECTABLE_ERR type:STREAM_VC phy:0 cil:0 st:0 vc:1 status:0x00000004
kworker/0:15-202     [000] ....   100.934588: rtcpu_nvcsi_intr: tstamp:3755875802 class:GLOBAL type:STREAM_VC phy:0 cil:0 st:0 vc:1 status:0x00000004
kworker/0:15-202     [000] ....   100.934588: rtcpu_nvcsi_intr: tstamp:3755875802 class:CORRECTABLE_ERR type:STREAM_VC phy:0 cil:0 st:0 vc:1 status:0x00000004
kworker/0:15-202     [000] ....   100.934588: rtcpu_nvcsi_intr: tstamp:3755882349 class:GLOBAL type:STREAM_VC phy:0 cil:0 st:0 vc:1 status:0x00000004
kworker/0:15-202     [000] ....   100.934589: rtcpu_nvcsi_intr: tstamp:3755882349 class:CORRECTABLE_ERR type:STREAM_VC phy:0 cil:0 st:0 vc:1 status:0x00000004
kworker/0:15-202     [000] ....   100.934589: rtcpu_nvcsi_intr: tstamp:3755929373 class:GLOBAL type:STREAM_VC phy:0 cil:0 st:0 vc:1 status:0x00000004
kworker/0:15-202     [000] ....   100.934589: rtcpu_nvcsi_intr: tstamp:3755929373 class:CORRECTABLE_ERR type:STREAM_VC phy:0 cil:0 st:0 vc:1 status:0x00000004
kworker/0:15-202     [000] ....   100.934590: rtcpu_nvcsi_intr: tstamp:3755945099 class:GLOBAL type:STREAM_VC phy:0 cil:0 st:0 vc:1 status:0x00000008
kworker/0:15-202     [000] ....   100.934590: rtcpu_nvcsi_intr: tstamp:3755945099 class:CORRECTABLE_ERR type:STREAM_VC phy:0 cil:0 st:0 vc:1 status:0x00000008
kworker/0:15-202     [000] ....   100.934590: rtcpu_nvcsi_intr: tstamp:3755945675 class:GLOBAL type:STREAM_VC phy:0 cil:0 st:0 vc:0 status:0x00000004
kworker/0:15-202     [000] ....   100.934591: rtcpu_nvcsi_intr: tstamp:3755945675 class:CORRECTABLE_ERR type:STREAM_VC phy:0 cil:0 st:0 vc:0 status:0x00000004
kworker/0:15-202     [000] ....   100.934591: rtcpu_nvcsi_intr: tstamp:3755950802 class:GLOBAL type:STREAM_VC phy:0 cil:0 st:0 vc:1 status:0x00000004
kworker/0:15-202     [000] ....   100.934591: rtcpu_nvcsi_intr: tstamp:3755950802 class:CORRECTABLE_ERR type:STREAM_VC phy:0 cil:0 st:0 vc:1 status:0x00000004
kworker/0:15-202     [000] ....   100.934592: rtcpu_nvcsi_intr: tstamp:3755977586 class:GLOBAL type:STREAM_VC phy:0 cil:0 st:0 vc:1 status:0x00000004
kworker/0:15-202     [000] ....   100.934592: rtcpu_nvcsi_intr: tstamp:3755977586 class:CORRECTABLE_ERR type:STREAM_VC phy:0 cil:0 st:0 vc:1 status:0x00000004
kworker/0:15-202     [000] ....   100.934592: rtcpu_nvcsi_intr: tstamp:3756020099 class:GLOBAL type:STREAM_VC phy:0 cil:0 st:0 vc:1 status:0x00000008
kworker/0:15-202     [000] ....   100.934593: rtcpu_nvcsi_intr: tstamp:3756020099 class:CORRECTABLE_ERR type:STREAM_VC phy:0 cil:0 st:0 vc:1 status:0x00000008
kworker/0:15-202     [000] ....   100.934593: rtcpu_nvcsi_intr: tstamp:3756020675 class:GLOBAL type:STREAM_VC phy:0 cil:0 st:0 vc:0 status:0x00000004
kworker/0:15-202     [000] ....   100.934593: rtcpu_nvcsi_intr: tstamp:3756020675 class:CORRECTABLE_ERR type:STREAM_VC phy:0 cil:0 st:0 vc:0 status:0x00000004
kworker/0:15-202     [000] ....   100.934594: rtcpu_nvcsi_intr: tstamp:3756025801 class:GLOBAL type:STREAM_VC phy:0 cil:0 st:0 vc:1 status:0x00000004
kworker/0:15-202     [000] ....   100.934594: rtcpu_nvcsi_intr: tstamp:3756025801 class:CORRECTABLE_ERR type:STREAM_VC phy:0 cil:0 st:0 vc:1 status:0x00000004
kworker/0:15-202     [000] ....   100.934594: rtcpu_nvcsi_intr: tstamp:3756052585 class:GLOBAL type:STREAM_VC phy:0 cil:0 st:0 vc:1 status:0x00000004
35

hi
After using the following command, my current parameters can be displayed. What is the problem and how should I handle it?
thank you!

36

hello 305248199,

below is the latest logs with boosting clocks?

it is the error reported with packet payload CRC check failed.
you may double check the SerDes chip output configurations, since you’ve validate with lower data-rate.

37

yes

After using the following command, it can be displayed normally

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

38

hi JerryChang！

How to handle this situation?

39

The configuration of the 4 cameras has not been modified. I only did the mipi rate improvement configuration for the max96712 serial device (0x415, 0x418 register configuration is 0x34), and no other modifications were made.

40

hello 305248199,

it’s ignore clock rate settings in device tree when you boosting system clocks.
so..

you should also update device tree settings accordingly.

41

hi JerryChang，
Excuse me, where can I modify it in the device tree?

thk~

42

majorly, you should review serdes_pix_clk_hz device tree property settings.