tx2 r28.2.1 with adv7282m driver failed

I can’t tell what going on with this. It’s better consult with device vendor.

hello @ShaneCCC, i apply a eval adv7282a-m board,and it work fine on our other platform. but when i connect it with tx2, i find the csi receiver cant deinterlacer mipi data right. could u give some advice?

Have a check below wiki if any help.

https://elinux.org/Jetson_TX2_Camera_BringUp

i trace the debug messag:

tracer: nop

entries-in-buffer/entries-written: 121/121 #P:6

_-----=> irqs-off

/ _----=> need-resched

| / _—=> hardirq/softirq

|| / _–=> preempt-depth

||| / delay

TASK-PID CPU# |||| TIMESTAMP FUNCTION

| | | |||| | |

 kworker/5:2-2790  [005] ...1  8923.514486: rtos_queue_peek_from_isr_failed: tstamp:279215254901 queue:0x0b4a3c58
 kworker/5:2-2790  [005] ...1  8923.514491: rtcpu_start: tstamp:279215255977
 kworker/5:2-2790  [005] ...1  8923.514492: rtcpu_vinotify_handle_msg: tstamp:279215347598 tag:CSIMUX_STREAM channel:0xff frame:0 vi_tstamp:42472912 data:0x00000100
 kworker/5:2-2790  [005] ...1  8923.514493: rtcpu_vinotify_handle_msg: tstamp:279215428692 tag:CHANSEL_PXL_SOF channel:0x00 frame:2 vi_tstamp:42553881 data:0x00000001
 kworker/5:2-2790  [005] ...1  8923.514494: rtcpu_vinotify_handle_msg: tstamp:279215428888 tag:ATOMP_FS channel:0x00 frame:2 vi_tstamp:42553911 data:0x00000000
 kworker/5:2-2790  [005] ...1  8923.514495: rtcpu_vinotify_handle_msg: tstamp:279215431047 tag:CHANSEL_LOAD_FRAMED channel:0x04 frame:2 vi_tstamp:42556378 data:0x08000000
 kworker/5:2-2790  [005] ...1  8923.566492: rtcpu_vinotify_handle_msg: tstamp:279216004346 tag:CHANSEL_PXL_EOF channel:0x00 frame:2 vi_tstamp:43129488 data:0x023f0002
 kworker/5:2-2790  [005] ...1  8923.566498: rtcpu_vinotify_handle_msg: tstamp:279216004500 tag:ATOMP_FE channel:0x00 frame:2 vi_tstamp:43129535 data:0x00000000
 kworker/5:2-2790  [005] ...1  8923.566499: rtcpu_vinotify_handle_msg: tstamp:279216013332 tag:CSIMUX_STREAM channel:0xff frame:0 vi_tstamp:43138656 data:0x00000100
 kworker/5:2-2790  [005] ...1  8923.566500: rtcpu_vinotify_handle_msg: tstamp:279216638132 tag:CSIMUX_STREAM channel:0xff frame:0 vi_tstamp:43763420 data:0x00000100
 kworker/5:2-2790  [005] ...1  8923.618521: rtcpu_vinotify_handle_msg: tstamp:279217262853 tag:CSIMUX_STREAM channel:0xff frame:0 vi_tstamp:44388184 data:0x00000100
 kworker/5:2-2790  [005] ...1  8923.618526: rtcpu_vinotify_handle_msg: tstamp:279217887639 tag:CSIMUX_STREAM channel:0xff frame:0 vi_tstamp:45012948 data:0x00000100
 kworker/5:2-2790  [005] ...1  8923.618529: rtcpu_vinotify_handle_msg: tstamp:279218512403 tag:CSIMUX_STREAM channel:0xff frame:0 vi_tstamp:45637712 data:0x00000100
 kworker/5:2-2790  [005] ...1  8923.670525: rtcpu_vinotify_handle_msg: tstamp:279219137333 tag:CSIMUX_STREAM channel:0xff frame:0 vi_tstamp:46262476 data:0x00000100
 kworker/5:2-2790  [005] ...1  8923.670532: rtcpu_vinotify_handle_msg: tstamp:279219762102 tag:CSIMUX_STREAM channel:0xff frame:0 vi_tstamp:46887240 data:0x00000100
 kworker/5:2-2790  [005] ...1  8923.670552: rtos_queue_peek_from_isr_failed: tstamp:279220255970 queue:0x0b4a3c58
 kworker/5:2-2790  [005] ...1  8923.670557: rtcpu_vinotify_handle_msg: tstamp:279220386865 tag:CSIMUX_STREAM channel:0xff frame:0 vi_tstamp:47512004 data:0x00000100
 kworker/5:2-2790  [005] ...1  8923.722538: rtcpu_vinotify_handle_msg: tstamp:279221011629 tag:CSIMUX_STREAM channel:0xff frame:0 vi_tstamp:48136768 data:0x00000100
 kworker/5:2-2790  [005] ...1  8923.722547: rtcpu_vinotify_handle_msg: tstamp:279221636404 tag:CSIMUX_STREAM channel:0xff frame:0 vi_tstamp:48761532 data:0x00000100
 kworker/5:2-2790  [005] ...1  8923.774524: rtcpu_vinotify_handle_msg: tstamp:279222261158 tag:CSIMUX_STREAM channel:0xff frame:0 vi_tstamp:49386296 data:0x00000100
 kworker/5:2-2790  [005] ...1  8923.774530: rtcpu_vinotify_handle_msg: tstamp:279222885919 tag:CSIMUX_STREAM channel:0xff frame:0 vi_tstamp:50011060 data:0x00000100
 kworker/5:2-2790  [005] ...1  8923.774535: rtcpu_vinotify_handle_msg: tstamp:279223510688 tag:CSIMUX_STREAM channel:0xff frame:0 vi_tstamp:50635824 data:0x00000100
 kworker/5:2-2790  [005] ...1  8923.826661: rtcpu_vinotify_handle_msg: tstamp:279224135448 tag:CSIMUX_STREAM channel:0xff frame:0 vi_tstamp:51260588 data:0x00000100
 kworker/5:2-2790  [005] ...1  8923.826682: rtcpu_vinotify_handle_msg: tstamp:279224760229 tag:CSIMUX_STREAM channel:0xff frame:0 vi_tstamp:51885352 data:0x00000100
 kworker/5:2-2790  [005] ...1  8923.826697: rtos_queue_peek_from_isr_failed: tstamp:279225256482 queue:0x0b4a3c58
 kworker/5:2-2790  [005] ...1  8923.878558: rtcpu_vinotify_handle_msg: tstamp:279225384978 tag:CSIMUX_STREAM channel:0xff frame:0 vi_tstamp:52510117 data:0x00000100
 kworker/5:2-2790  [005] ...1  8923.878569: rtcpu_vinotify_handle_msg: tstamp:279226009774 tag:CSIMUX_STREAM channel:0xff frame:0 vi_tstamp:53134881 data:0x00000100
 kworker/5:2-2790  [005] ...1  8923.878574: rtcpu_vinotify_handle_msg: tstamp:279226634531 tag:CSIMUX_STREAM channel:0xff frame:0 vi_tstamp:53759645 data:0x00000100
 kworker/5:2-2790  [005] ...1  8923.930757: rtcpu_vinotify_handle_msg: tstamp:279227259291 tag:CSIMUX_STREAM channel:0xff frame:0 vi_tstamp:54384409 data:0x00000100
 kworker/5:2-2790  [005] ...1  8923.930772: rtcpu_vinotify_handle_msg: tstamp:279227884055 tag:CSIMUX_STREAM channel:0xff frame:0 vi_tstamp:55009173 data:0x00000100
 kworker/5:2-2790  [005] ...1  8923.930777: rtcpu_vinotify_handle_msg: tstamp:279228508823 tag:CSIMUX_STREAM channel:0xff frame:0 vi_tstamp:55633937 data:0x00000100
 kworker/5:2-2790  [005] ...1  8923.982614: rtcpu_vinotify_handle_msg: tstamp:279229133420 tag:CSIMUX_STREAM channel:0xff frame:0 vi_tstamp:56258701 data:0x00000100
 kworker/5:2-2790  [005] ...1  8923.982640: rtcpu_vinotify_handle_msg: tstamp:279229758354 tag:CSIMUX_STREAM channel:0xff frame:0 vi_tstamp:56883465 data:0x00000100

hello @ShaneCCC,my chip output 216m hz mipi clk, in other doc i find tx2 is 204mhz clk, is this a problem for my chip?

It’s doesn’t matter. 204 is vi logic run frequency it doesn’t matter with MIPI speed.

HI,@ShaneCCC,I use Oscilloscope catch the 7282am output signal, its a shortpack - line data pack - shortpack -line data pack, but i catch the ov5693 sigal ,it always a line data pack in a frame, is tx2 support 7282am’s frame format?

hi,@ShaneCCC,Now I got help from : https://devtalk.nvidia.com/default/topic/1032730/jetson-tx2/adv7280m-error-pxl_sof-syncpt-timeout-/post/5254339/
Now i can get a ful image,but the line data is not good, and i just can catch 25fps(output 50 fps), the tx2’s compatibility with pal chip is pool, do u have any idea to solve the problem?

Don’t know what you mean data line is not good.
Try to boost the vi clock to try the fps issue.

sudo ./jetson_clocks.sh
sudo su
echo 1 > /sys/kernel/debug/bpmp/debug/clk/vi/mrq_rate_locked
cat /sys/kernel/debug/bpmp/debug/clk/vi/max_rate
echo max_rate > /sys/kernel/debug/bpmp/debug/clk/vi/rate

hi,@ShaneCCC, I tried to clarify the problem.
1.when I Increase delay 20ms in tegra_channel_capture_frame, i can capture a Full frame,but it is something wrong with sample. then i use a fpga csi output 640x480 RGB color bar,tx2 can display well.but i force fpga output 720x576,The phenomenon is the same as adv7282a-m.the color bar is not alignment.
2.i open trace,use v4l2-ctl --stream-count=1 to capture one frame. v4l2 display captured one frame. but the debug message display tx2 received two CHANSEL_PXL_SOF … CHANSEL_PXL_EOF.so my Actual frame rate is half of chip output frame rate。
3.by the way, my fpga csi output 30 fps, but it is same as adv7282am,tx2 can only cap 15fps.
Look forward to your reply。

Check the timestamp of the CHANSEL_PXL_SOF and next CHANSEL_PXL_EOF (frame duration = CHANSEL_PXL_EOF - CHANSEL_PXL_SOF)

This is a frame informatio, Can you help me with the analysis?

kworker/0:1-114   [000] ...1    36.220553: rtos_queue_peek_from_isr_failed: tstamp:1465243139 queue:0x0b4a3c58
     kworker/0:1-114   [000] ...1    36.220560: rtcpu_start: tstamp:1465243963
     kworker/0:1-114   [000] ...1    36.220563: rtcpu_vinotify_handle_msg: tstamp:1465269494 tag:CSIMUX_STREAM channel:0xff frame:0 vi_tstamp:1465269078 data:0x00000001
     kworker/0:1-114   [000] ...1    36.220564: rtcpu_vinotify_handle_msg: tstamp:1465660795 tag:CHANSEL_PXL_SOF channel:0x00 frame:2796 vi_tstamp:1465660252 data:0x00000001
     kworker/0:1-114   [000] ...1    36.220565: rtcpu_vinotify_handle_msg: tstamp:1465660942 tag:ATOMP_FS channel:0x00 frame:2796 vi_tstamp:1465660257 data:0x00000000
     kworker/0:1-114   [000] ...1    36.220566: rtcpu_vinotify_handle_msg: tstamp:1465666157 tag:CHANSEL_LOAD_FRAMED channel:0x01 frame:2796 vi_tstamp:1465665749 data:0x08000000
     kworker/0:1-114   [000] ...1    36.220568: rtcpu_vinotify_handle_msg: tstamp:1466164020 tag:CHANSEL_PXL_EOF channel:0x00 frame:2796 vi_tstamp:1466163587 data:0x02cf0002
     kworker/0:1-114   [000] ...1    36.220569: rtcpu_vinotify_handle_msg: tstamp:1466167568 tag:ATOMP_FE channel:0x00 frame:2796 vi_tstamp:1466167106 data:0x00000000
     kworker/0:1-114   [000] ...1    36.272542: rtcpu_vinotify_handle_msg: tstamp:1466710474 tag:CHANSEL_PXL_SOF channel:0x00 frame:2798 vi_tstamp:1466709913 data:0x00000001
     kworker/0:1-114   [000] ...1    36.272550: rtcpu_vinotify_handle_msg: tstamp:1466710668 tag:ATOMP_FS channel:0x00 frame:2798 vi_tstamp:1466709919 data:0x00000000
     kworker/0:1-114   [000] ...1    36.272552: rtcpu_vinotify_handle_msg: tstamp:1466719414 tag:CHANSEL_LOAD_FRAMED channel:0x01 frame:2798 vi_tstamp:1466718970 data:0x08000000
     kworker/0:1-114   [000] ...1    36.272554: rtcpu_vinotify_handle_msg: tstamp:1467213681 tag:CHANSEL_PXL_EOF channel:0x00 frame:2798 vi_tstamp:1467213249 data:0x02cf0002
     kworker/0:1-114   [000] ...1    36.272556: rtcpu_vinotify_handle_msg: tstamp:1467217231 tag:ATOMP_FE channel:0x00 frame:2798 vi_tstamp:1467216767 data:0x00000000
     kworker/0:1-114   [000] ...1    36.272557: rtcpu_vinotify_handle_msg: tstamp:1467760133 tag:CHANSEL_PXL_SOF channel:0x00 frame:2800 vi_tstamp:1467759575 data:0x00000001
     kworker/0:1-114   [000] ...1    36.272559: rtcpu_vinotify_handle_msg: tstamp:1467760363 tag:ATOMP_FS channel:0x00 frame:2800 vi_tstamp:1467759581 data:0x00000000
     kworker/0:1-114   [000] ...1    36.325008: rtcpu_vinotify_handle_msg: tstamp:1468263366 tag:CHANSEL_PXL_EOF channel:0x00 frame:2800 vi_tstamp:1468262911 data:0x02cf0002
     kworker/0:1-114   [000] ...1    36.325022: rtcpu_vinotify_handle_msg: tstamp:1468266914 tag:ATOMP_FE channel:0x00 frame:2800 vi_tstamp:1468266430 data:0x00000000
     kworker/0:1-114   [000] ...1    36.325028: rtcpu_vinotify_handle_msg: tstamp:1468809820 tag:CHANSEL_PXL_SOF channel:0x00 frame:2802 vi_tstamp:1468809237 data:0x00000001
     kworker/0:1-114   [000] ...1    36.325032: rtcpu_vinotify_handle_msg: tstamp:1468810145 tag:ATOMP_FS channel:0x00 frame:2802 vi_tstamp:1468809242 data:0x00000000
     kworker/0:1-114   [000] ...1    36.325036: rtcpu_vinotify_handle_msg: tstamp:1469313027 tag:CHANSEL_PXL_EOF channel:0x00 frame:2802 vi_tstamp:1469312573 data:0x02cf0002

From the log the duration about 50ms, the fpga output is about 20fps.
Does boost the vi/emc clock not help?

This method didn’t work.I measure the oscilloscope output it is indeed a 60fps output.