8192*64 Mipi Data support on TX2

Autonomous Machines Jetson & Embedded Systems Jetson TX2
#1

Hi ShaneCCC,

We can capture 4096*128 resolution video through MIPI interface on Tx2.

We try to capture 8192*64 resolution video, but failed.

The trace info shows nothing abnormal.

The trace info:

kworker/0:0-4715  [000] ...1  5755.690024: rtcpu_vinotify_handle_msg: tstamp:180199058667 tag:CSIMUX_FRAME channel:0x00 frame:0 vi_tstamp:4105399120 data:0x000000a0
     kworker/0:0-4715  [000] ...1  5755.690031: rtcpu_vinotify_handle_msg: tstamp:180199443847 tag:CSIMUX_FRAME channel:0x00 frame:0 vi_tstamp:4105784301 data:0x000000a0
     kworker/0:0-4715  [000] ...1  5755.690036: rtos_queue_peek_from_isr_failed: tstamp:180199694054 queue:0x0b4a3c58
     kworker/0:0-4715  [000] ...1  5755.690039: rtcpu_vinotify_handle_msg: tstamp:180199829032 tag:CSIMUX_FRAME channel:0x00 frame:0 vi_tstamp:4106169486 data:0x000000a0
     kworker/0:0-4715  [000] ...1  5755.690041: rtcpu_vinotify_handle_msg: tstamp:180200214217 tag:CSIMUX_FRAME channel:0x00 frame:0 vi_tstamp:4106554671 data:0x000000a0
     kworker/0:0-4715  [000] ...1  5755.742010: rtcpu_vinotify_handle_msg: tstamp:180200599402 tag:CSIMUX_FRAME channel:0x00 frame:0 vi_tstamp:4106939856 data:0x000000a0
     kworker/0:0-4715  [000] ...1  5755.742017: rtcpu_vinotify_handle_msg: tstamp:180200984592 tag:CSIMUX_FRAME channel:0x00 frame:0 vi_tstamp:4107325038 data:0x000000a0
     kworker/0:0-4715  [000] ...1  5755.742020: rtcpu_vinotify_handle_msg: tstamp:180201369773 tag:CSIMUX_FRAME channel:0x00 frame:0 vi_tstamp:4107710222 data:0x000000a0
     kworker/0:0-4715  [000] ...1  5755.742022: rtcpu_vinotify_handle_msg: tstamp:180201754953 tag:CSIMUX_FRAME channel:0x00 frame:0 vi_tstamp:4108095407 data:0x000000a0
     kworker/0:0-4715  [000] ...1  5755.793996: rtcpu_vinotify_handle_msg: tstamp:180202140134 tag:CSIMUX_FRAME channel:0x00 frame:0 vi_tstamp:4108480590 data:0x000000a0
     kworker/0:0-4715  [000] ...1  5755.794002: rtcpu_vinotify_handle_msg: tstamp:180202525320 tag:CSIMUX_FRAME channel:0x00 frame:0 vi_tstamp:4108865775 data:0x000000a0
     kworker/0:0-4715  [000] ...1  5755.794005: rtcpu_vinotify_handle_msg: tstamp:180202910501 tag:CSIMUX_FRAME channel:0x00 frame:0 vi_tstamp:4109250958 data:0x000000a0
     kworker/0:0-4715  [000] ...1  5755.794007: rtcpu_vinotify_handle_msg: tstamp:180203295689 tag:CSIMUX_FRAME channel:0x00 frame:0 vi_tstamp:4109636144 data:0x000000a0
     kworker/0:0-4715  [000] ...1  5755.846013: rtcpu_vinotify_handle_msg: tstamp:180203680870 tag:CSIMUX_FRAME channel:0x00 frame:0 vi_tstamp:4110021325 data:0x000000a0
     kworker/0:0-4715  [000] ...1  5755.846018: rtcpu_vinotify_handle_msg: tstamp:180204066055 tag:CSIMUX_FRAME channel:0x00 frame:0 vi_tstamp:4110406511 data:0x000000a0
     kworker/0:0-4715  [000] ...1  5755.846020: rtcpu_vinotify_handle_msg: tstamp:180204451255 tag:CSIMUX_FRAME channel:0x00 frame:0 vi_tstamp:4110791696 data:0x000000a0
     kworker/0:0-4715  [000] ...1  5755.846025: rtos_queue_peek_from_isr_failed: tstamp:180204694534 queue:0x0b4a3c58
     kworker/0:0-4715  [000] ...1  5755.846028: rtcpu_vinotify_handle_msg: tstamp:180204836421 tag:CSIMUX_FRAME channel:0x00 frame:0 vi_tstamp:4111176877 data:0x000000a0
     kworker/0:0-4715  [000] ...1  5755.897996: rtcpu_vinotify_handle_msg: tstamp:180205221607 tag:CSIMUX_FRAME channel:0x00 frame:0 vi_tstamp:4111562064 data:0x000000a0
     kworker/0:0-4715  [000] ...1  5755.898001: rtcpu_vinotify_handle_msg: tstamp:180205606791 tag:CSIMUX_FRAME channel:0x00 frame:0 vi_tstamp:4111947246 data:0x000000a0
     kworker/0:0-4715  [000] ...1  5755.898002: rtcpu_vinotify_handle_msg: tstamp:180205991974 tag:CSIMUX_FRAME channel:0x00 frame:0 vi_tstamp:4112332430 data:0x000000a0
     kworker/0:0-4715  [000] ...1  5755.898003: rtcpu_vinotify_handle_msg: tstamp:180206377170 tag:CSIMUX_FRAME channel:0x00 frame:0 vi_tstamp:4112717615 data:0x000000a0
     kworker/0:0-4715  [000] ...1  5755.898005: rtcpu_vinotify_handle_msg: tstamp:180206762343 tag:CSIMUX_FRAME channel:0x00 frame:0 vi_tstamp:4113102798 data:0x000000a0
     kworker/0:0-4715  [000] ...1  5755.950001: rtcpu_vinotify_handle_msg: tstamp:180207147529 tag:CSIMUX_FRAME channel:0x00 frame:0 vi_tstamp:4113487983 data:0x000000a0
     kworker/0:0-4715  [000] ...1  5755.950003: rtcpu_vinotify_handle_msg: tstamp:180207532714 tag:CSIMUX_FRAME channel:0x00 frame:0 vi_tstamp:4113873167 data:0x000000a0
     kworker/0:0-4715  [000] ...1  5755.950004: rtcpu_vinotify_handle_msg: tstamp:180207917899 tag:CSIMUX_FRAME channel:0x00 frame:0 vi_tstamp:4114258351 data:0x000000a0
     kworker/0:0-4715  [000] ...1  5755.950005: rtcpu_vinotify_handle_msg: tstamp:180208303079 tag:CSIMUX_FRAME channel:0x00 frame:0 vi_tstamp:4114643535 data:0x000000a0
     kworker/0:0-4715  [000] ...1  5756.001961: rtcpu_vinotify_handle_msg: tstamp:180208688265 tag:CSIMUX_FRAME channel:0x00 frame:0 vi_tstamp:4115028720 data:0x000000a0
     kworker/0:0-4715  [000] ...1  5756.001965: rtcpu_vinotify_handle_msg: tstamp:180209073458 tag:CSIMUX_FRAME channel:0x00 frame:0 vi_tstamp:4115413902 data:0x000000a0
     kworker/0:0-4715  [000] ...1  5756.001966: rtcpu_vinotify_handle_msg: tstamp:180209458634 tag:CSIMUX_FRAME channel:0x00 frame:0 vi_tstamp:4115799087 data:0x000000a0

and dmesg info:

[ 6255.606156] nvcsi 150c0000.nvcsi: csi4_stream_check_status (0) ERROR_STATUS2VI_VC0 = 0x00000002
[ 6255.614975] nvcsi 150c0000.nvcsi: csi4_stream_check_status (0) ERROR_STATUS2VI_VC2 = 0x00000002
[ 6255.623731] nvcsi 150c0000.nvcsi: csi4_stream_check_status (0) INTR_STATUS 0x00000202
[ 6255.631613] nvcsi 150c0000.nvcsi: csi4_stream_check_status (0) ERR_INTR_STATUS 0x00000202
[ 6255.639876] nvcsi 150c0000.nvcsi: csi4_cil_check_status (0) CIL_INTR_STATUS 0x00000156
[ 6255.647853] nvcsi 150c0000.nvcsi: csi4_cil_check_status (0) CIL_ERR_INTR_STATUS 0x00000156
[ 6256.653985] tegra-vi4 15700000.vi: PXL_SOF syncpt timeout! err = -11

Is there any limits on this ? @ShaneCCC

Thanks.

#2

There’s no this limition.
Looks like the transaction have multiple bit error.

[ 6255.647853] nvcsi 150c0000.nvcsi: csi4_cil_check_status (0) CIL_ERR_INTR_STATUS 0x00000156

#3

Hi ShaneCCC
You mean that 8192*64 resolution video is not meet the mipi spec?

#4

Yes, may this setting have signal issue.

#5

@ShaneCCC ,thanks for your reply.
Have you ever tried resolution video more than 4096 ?
we try to get 8192*32/64/128 resolution video, but failed。

#6

Do you mean the width more than 4096? Yes, but height is not like this.
And do you capture by v4l2-ctl?

#7

@ShaneCCC
Yes, I mean the width more than 4096.
We capture by coding according v4l2.
Could you give me a resolution video that more than 4096 ? I try it

#8

You can check the ov23850, the resolution is 5632*3168

#9

@ShaneCCC,thanks for your reply.
Now, I can get data resolution video for width with 8192,
Could it support for resolution video with 16384 or 32768?