Read Mipi data in 2.5 Gbps using Xavier NX

Hi Everyone,
I need to read mipi data in 2.5Gbps using following specification.
Lane Configuration : 3 * 4
Data Resolution : 60k * 1(width * Height) → Custom data
speed : 2.5Gbps
When I was trying to read data it’s populating following trace log

 kworker/0:0-4     [000] ....   439.124315: rtcpu_nvcsi_intr: tstamp:14233338362 class:CORRECTABLE_ERR type:PHY_INTR phy:1 cil:0 st:0 vc:0 status:0x00000004
 kworker/0:0-4     [000] ....   439.124316: rtcpu_nvcsi_intr: tstamp:14233344825 class:GLOBAL type:PHY_INTR0 phy:1 cil:0 st:0 vc:0 status:0x00000004
 kworker/0:0-4     [000] ....   439.124316: rtcpu_nvcsi_intr: tstamp:14233344825 class:CORRECTABLE_ERR type:PHY_INTR phy:1 cil:0 st:0 vc:0 status:0x00000004
 kworker/0:0-4     [000] ....   439.124316: rtcpu_nvcsi_intr: tstamp:14233357272 class:GLOBAL type:PHY_INTR0 phy:1 cil:0 st:0 vc:0 status:0x00000004
 kworker/0:0-4     [000] ....   439.124317: rtcpu_nvcsi_intr: tstamp:14233357272 class:CORRECTABLE_ERR type:PHY_INTR phy:1 cil:0 st:0 vc:0 status:0x00000004
 kworker/0:0-4     [000] ....   439.124317: rtcpu_nvcsi_intr: tstamp:14233386992 class:GLOBAL type:PHY_INTR0 phy:1 cil:0 st:0 vc:0 status:0x00000004
 kworker/0:0-4     [000] ....   439.124317: rtcpu_nvcsi_intr: tstamp:14233386992 class:CORRECTABLE_ERR type:PHY_INTR phy:1 cil:0 st:0 vc:0 status:0x00000004
 kworker/0:0-4     [000] ....   439.124318: rtcpu_nvcsi_intr: tstamp:14233423030 class:GLOBAL type:PHY_INTR0 phy:1 cil:0 st:0 vc:0 status:0x00000004
 kworker/0:0-4     [000] ....   439.124318: rtcpu_nvcsi_intr: tstamp:14233423030 class:CORRECTABLE_ERR type:PHY_INTR phy:1 cil:0 st:0 vc:0 status:0x00000004
 kworker/0:0-4     [000] ....   439.124318: rtcpu_nvcsi_intr: tstamp:14233446653 class:GLOBAL type:PHY_INTR0 phy:1 cil:0 st:0 vc:0 status:0x00000004
 kworker/0:0-4     [000] ....   439.124319: rtcpu_nvcsi_intr: tstamp:14233446653 class:CORRECTABLE_ERR type:PHY_INTR phy:1 cil:0 st:0 vc:0 status:0x00000004
 kworker/0:0-4     [000] ....   439.124319: rtcpu_nvcsi_intr: tstamp:14233453348 class:GLOBAL type:PHY_INTR0 phy:1 cil:0 st:0 vc:0 status:0x00000004
 kworker/0:0-4     [000] ....   439.124319: rtcpu_nvcsi_intr: tstamp:14233453348 class:CORRECTABLE_ERR type:PHY_INTR phy:1 cil:0 st:0 vc:0 status:0x00000004
 kworker/0:0-4     [000] ....   439.124320: rtcpu_nvcsi_intr: tstamp:14233501338 class:GLOBAL type:PHY_INTR0 phy:1 cil:0 st:0 vc:0 status:0x02000000
 kworker/0:0-4     [000] ....   439.124320: rtcpu_nvcsi_intr: tstamp:14233501338 class:CORRECTABLE_ERR type:PHY_INTR phy:1 cil:0 st:0 vc:0 status:0x00000200
 kworker/0:0-4     [000] ....   439.124320: rtcpu_nvcsi_intr: tstamp:14233561288 class:GLOBAL type:PHY_INTR0 phy:1 cil:0 st:0 vc:0 status:0x00000004
 kworker/0:0-4     [000] ....   439.124321: rtcpu_nvcsi_intr: tstamp:14233561288 class:CORRECTABLE_ERR type:PHY_INTR phy:1 cil:0 st:0 vc:0 status:0x00000004
 kworker/0:0-4     [000] ....   439.124321: rtcpu_nvcsi_intr: tstamp:14233567484 class:GLOBAL type:PHY_INTR0 phy:1 cil:0 st:0 vc:0 status:0x00000004
 kworker/0:0-4     [000] ....   439.124321: rtcpu_nvcsi_intr: tstamp:14233567484 class:CORRECTABLE_ERR type:PHY_INTR phy:1 cil:0 st:0 vc:0 status:0x00000004
 kworker/0:0-4     [000] ....   439.124322: rtcpu_nvcsi_intr: tstamp:14233597294 class:GLOBAL type:PHY_INTR0 phy:1 cil:0 st:0 vc:0 status:0x00000004
 kworker/0:0-4     [000] ....   439.124322: rtcpu_nvcsi_intr: tstamp:14233597294 class:CORRECTABLE_ERR type:PHY_INTR phy:1 cil:0 st:0 vc:0 status:0x00000004
 kworker/0:0-4     [000] ....   439.124322: rtcpu_nvcsi_intr: tstamp:14233627049 class:GLOBAL type:PHY_INTR0 phy:1 cil:0 st:0 vc:0 status:0x00000004
 kworker/0:0-4     [000] ....   439.124323: rtcpu_nvcsi_intr: tstamp:14233627049 class:CORRECTABLE_ERR type:PHY_INTR phy:1 cil:0 st:0 vc:0 status:0x00000004
 kworker/0:0-4     [000] ....   439.124323: rtcpu_nvcsi_intr: tstamp:14233663489 class:GLOBAL type:PHY_INTR0 phy:1 cil:0 st:0 vc:0 status:0x00000004
 kworker/0:0-4     [000] ....   439.124323: rtcpu_nvcsi_intr: tstamp:14233663489 class:CORRECTABLE_ERR type:PHY_INTR phy:1 cil:0 st:0 vc:0 status:0x00000004
 kworker/0:0-4     [000] ....   439.124324: rtcpu_nvcsi_intr: tstamp:14233669503 class:GLOBAL type:PHY_INTR0 phy:1 cil:0 st:0 vc:0 status:0x00000004
 kworker/0:0-4     [000] ....   439.124324: rtcpu_nvcsi_intr: tstamp:14233669503 class:CORRECTABLE_ERR type:PHY_INTR phy:1 cil:0 st:0 vc:0 status:0x00000004
 kworker/0:0-4     [000] ....   439.180313: rtcpu_nvcsi_intr: tstamp:14233681806 class:GLOBAL type:PHY_INTR0 phy:1 cil:0 st:0 vc:0 status:0x02000000
 kworker/0:0-4     [000] ....   439.180314: rtcpu_nvcsi_intr: tstamp:14233681806 class:CORRECTABLE_ERR type:PHY_INTR phy:1 cil:0 st:0 vc:0 status:0x00000200
 kworker/0:0-4     [000] ....   439.180314: rtcpu_nvcsi_intr: tstamp:14233718657 class:GLOBAL type:PHY_INTR0 phy:1 cil:0 st:0 vc:0 status:0x00000004
 kworker/0:0-4     [000] ....   439.180315: rtcpu_nvcsi_intr: tstamp:14233718657 class:CORRECTABLE_ERR type:PHY_INTR phy:1 cil:0 st:0 vc:0 status:0x00000004
 kworker/0:0-4     [000] ....   439.180315: rtcpu_nvcsi_intr: tstamp:14233747890 class:GLOBAL type:PHY_INTR0 phy:1 cil:0 st:0 vc:0 status:0x00000004
 kworker/0:0-4     [000] ....   439.180315: rtcpu_nvcsi_intr: tstamp:14233747890 class:CORRECTABLE_ERR type:PHY_INTR phy:1 cil:0 st:0 vc:0 status:0x00000004
 kworker/0:0-4     [000] ....   439.180316: rtcpu_nvcsi_intr: tstamp:14233777737 class:GLOBAL type:PHY_INTR0 phy:1 cil:0 st:0 vc:0 status:0x00000004
 kworker/0:0-4     [000] ....   439.180316: rtcpu_nvcsi_intr: tstamp:14233777737 class:CORRECTABLE_ERR type:PHY_INTR phy:1 cil:0 st:0 vc:0 status:0x00000004
 kworker/0:0-4     [000] ....   439.180316: rtcpu_nvcsi_intr: tstamp:14233796369 class:GLOBAL type:PHY_INTR0 phy:1 cil:0 st:0 vc:0 status:0x02000000
 kworker/0:0-4     [000] ....   439.180317: rtcpu_nvcsi_intr: tstamp:14233796369 class:CORRECTABLE_ERR type:PHY_INTR phy:1 cil:0 st:0 vc:0 status:0x00000200
 kworker/0:0-4     [000] ....   439.180317: rtcpu_nvcsi_intr: tstamp:14233856050 class:GLOBAL type:PHY_INTR0 phy:1 cil:0 st:0 vc:0 status:0x00000004
 kworker/0:0-4     [000] ....   439.180317: rtcpu_nvcsi_intr: tstamp:14233856050 class:CORRECTABLE_ERR type:PHY_INTR phy:1 cil:0 st:0 vc:0 status:0x00000004
 kworker/0:0-4     [000] ....   439.180318: rtcpu_nvcsi_intr: tstamp:14233868629 class:GLOBAL type:PHY_INTR0 phy:1 cil:0 st:0 vc:0 status:0x00000004
 kworker/0:0-4     [000] ....   439.180318: rtcpu_nvcsi_intr: tstamp:14233868629 class:CORRECTABLE_ERR type:PHY_INTR phy:1 cil:0 st:0 vc:0 status:0x00000004
 kworker/0:0-4     [000] ....   439.180318: rtcpu_nvcsi_intr: tstamp:14233898369 class:GLOBAL type:PHY_INTR0 phy:1 cil:0 st:0 vc:0 status:0x02000000
 kworker/0:0-4     [000] ....   439.180319: rtcpu_nvcsi_intr: tstamp:14233898369 class:CORRECTABLE_ERR type:PHY_INTR phy:1 cil:0 st:0 vc:0 status:0x00000200
 kworker/0:0-4     [000] ....   439.180319: rtcpu_nvcsi_intr: tstamp:14233934656 class:GLOBAL type:PHY_INTR0 phy:1 cil:0 st:0 vc:0 status:0x00000004
 kworker/0:0-4     [000] ....   439.180319: rtcpu_nvcsi_intr: tstamp:14233934656 class:CORRECTABLE_ERR type:PHY_INTR phy:1 cil:0 st:0 vc:0 status:0x00000004
 kworker/0:0-4     [000] ....   439.180320: rtcpu_nvcsi_intr: tstamp:14233958165 class:GLOBAL type:PHY_INTR0 phy:1 cil:0 st:0 vc:0 status:0x00000004
 kworker/0:0-4     [000] ....   439.180320: rtcpu_nvcsi_intr: tstamp:14233958165 class:CORRECTABLE_ERR type:PHY_INTR phy:1 cil:0 st:0 vc:0 status:0x00000004
 kworker/0:0-4     [000] ....   439.180320: rtcpu_nvcsi_intr: tstamp:14233964411 class:GLOBAL type:PHY_INTR0 phy:1 cil:0 st:0 vc:0 status:0x00000004
 kworker/0:0-4     [000] ....   439.180321: rtcpu_nvcsi_intr: tstamp:14233964411 class:CORRECTABLE_ERR type:PHY_INTR phy:1 cil:0 st:0 vc:0 status:0x00000004
 kworker/0:0-4     [000] ....   439.180321: rtcpu_nvcsi_intr: tstamp:14234043093 class:GLOBAL type:PHY_INTR0 phy:1 cil:0 st:0 vc:0 status:0x00000004
 kworker/0:0-4     [000] ....   439.180321: rtcpu_nvcsi_intr: tstamp:14234043093 class:CORRECTABLE_ERR type:PHY_INTR phy:1 cil:0 st:0 vc:0 status:0x00000004

Can you please help me to debug it.

Here I have attached my dtsi file for reference, This file working for 900 & 1350 Mbps.

regards
Albin Raj R Jtegra194-camera-radarV01-a00.dtsi (69.8 KB)

Moving to Jetson Xavier NX forum.

here’s see-also discussion thread.

hello PaulEnoch,

according to Jetson Xavier NX Product Design Guide,
[Chapter 8. MIPI CSI Video Input], each data lane has a peak bandwidth of up to 2.5 Gbps.
your configuration has above the peak bandwidth.
for example,

		* max_lane_speed = <>;
		* Max lane speed in Kbit/s

		max_lane_speed = <4000000>;

BTW,
this is used for bandwidth calculation,
you may revise max lane speed and please also have a try to keep this as default setting.
thanks

		vi_peak_byte_per_pixel = <1>;//RAW 8 Configuration = 1 pixel = 8bit = 1byte

Hi JerryChang,
Thanks for your support. I tried but it’s not helping still not able to read 2.5Gbps data.

Where to get the details of trace log register example ```
GLOBAL type:PHY_INTR0


thanks for your time

Hi JerryChang,
How to get these trace log details.

 kworker/0:0-4     [000] ....   439.180318: rtcpu_nvcsi_intr: tstamp:14233868629 class:CORRECTABLE_ERR type:PHY_INTR phy:1 cil:0 st:0 vc:0 status:0x00000004
 kworker/0:0-4     [000] ....   439.180318: rtcpu_nvcsi_intr: tstamp:14233898369 class:GLOBAL type:PHY_INTR0 phy:1 cil:0 st:0 vc:0 status:0x02000000

hello PaulEnoch,

sorry, there’s no public documentation to include the details for VI tracing logs.