csi2 timing issue of six OV5693 cameras on tx1

Hi,
I have made my camera expanding board using FPC to connect with ov5693 cameras.The length of FPC is 150mm. And the i2c mus is pca9548. The i2c works fine and kernel find all cameras.
But when i use gst-launch-1.0 to preview, only one camera of which mipi pcb line is the shortest can output video. The others 5 cameras output error:

nvidia@tegra-ubuntu:~$ gst-launch-1.0 nvcamerasrc fpsRange=“30.0 30.0” ! ‘video/x-raw(memory:NVMM), width=(int)1280, height=(int)720, format=(string)I420, framerate=(fraction)30/1’ ! nvtee ! nvvidconv flip-method=2 ! ‘video/x-raw(memory:NVMM), format=(string)I420’ ! nvoverlaysink -e
Setting pipeline to PAUSED …
[ 652.578448] nvcamera-daemon[1770]: unhandled level 2 translation fault (11) at 0x00000000, esr 0x92000006
[ 652.588535] pgd = ffffffc0c1834000
[ 652.591969] [00000000] *pgd=0000000141833003, *pud=0000000141833003, *pmd=0000000000000000
[ 652.600291]
[ 652.601790] CPU: 2 PID: 1770 Comm: nvcamera-daemon Not tainted 4.4.38 #33
[ 652.608600] Hardware name: jetson_tx1 (DT)
[ 652.612750] task: ffffffc0f4c88000 ti: ffffffc078a60000 task.ti: ffffffc078a60000
[ 652.620942] PC is at 0x402efc
[ 652.624053] LR is at 0x402ef8
[ 652.628108] pc : [<0000000000402efc>] lr : [<0000000000402ef8>] pstate: 60000000
[ 652.635665] sp : 0000007f8b9b12d0
[ 652.639026] x29: 0000007f8b9b59d0 x28: 0000000000000000
[ 652.644526] x27: 0000000000000006 x26: 0000007f8b9b5340
[ 652.649961] x25: 0000000000404000 x24: 0000000000000334
[ 652.655358] x23: 0000007f8b9b3340 x22: 0000007f8b9b2340
[ 652.660735] x21: 0000007f8b9b3264 x20: 0000007f8b9b1350
[ 652.667367] x19: 0000007f8b9b3950 x18: 0000000000000014
[ 652.672726] x17: 0000007f8d225fb0 x16: 0000007f8cf7a540
[ 652.678097] x15: 0000007f8dc06000 x14: 7265766972446172
[ 652.683434] x13: 656d61432f697061 x12: 2f637273206d6f72
[ 652.688760] x11: 6620676e69746167 x10: 61706f7270282020
[ 652.694091] x9 : 3a726574656d6172 x8 : 0000000000000040
[ 652.699428] x7 : 0000007f84d2b8d0 x6 : 0000000000000001
[ 652.704760] x5 : 0000000000000000 x4 : 0000007f84000b10
[ 652.710092] x3 : 0000000000000000 x2 : 0000000000000001
[ 652.715496] x1 : 0000000000000000 x0 : 0000000000000000
[ 652.720894]
[ 652.723009] Library at 0x402efc: 0x400000 /usr/sbin/nvcamera-daemon
[ 652.730424] Library at 0x402ef8: 0x400000 /usr/sbin/nvcamera-daemon
[ 652.736915] vdso base = 0x7f8dc05000
Socket read error. Camera Daemon stopped functioning…
gst_nvcamera_open() failed ret=0
ERROR: Pipeline doesn’t want to pause.
Setting pipeline to NULL …
Freeing pipeline …

I think the problem maybe the mipi timing(maybe the length of mipi line is too long). What should i do to tune the mipi timing to solve this problem.

Hi,
When run v4l2-ctl -d /dev/video0 --stream-mmap --stream-count=1 --stream-to=test.raw
The normal camera will be blocked by “csi calibration”.
Should i use devmem2 to tune the csi?

Hi,
I try cmd:
v4l2-ctl -d /dev/video1 --set-fmt-video=width=1280, height=720, pixelformat=RG10 --set-ctrl bypass_mode=0 --stream-mmap --stream-count=50 --stream-to=ov5693.raw
I could can get pics from all cams. But i use imagej to open,the pic is ok without color.
Using gst-launch-1.0 to preview still have unhandled level 2 translation fault.
I have no idea.

hello wjljy1,

may i know which JetPack release you’re working on?
since you had made camera expanding board to connect sensors with distance.
could you measure all the camera signaling with the oscilloscope, please check the settle time between each sensor.
thanks

Thanks for reply,
Later i will test the signal.I use the TX1. BTW what’s the “csi auto calculation” do and which reg is affected?

hello wjljy1,

thanks, waiting for your h/w measuring result.
may i know which JetPack release you’re working on? is it JetPack-3.1?

what’s the “csi auto calculation” do and which reg is affected?
could you share the kernel message?
thanks

Hi JerryChang,
yes , JetPack-3.1.
JetPack-3.1
The h/w measuring as follow.
https://pan.baidu.com/s/1c28RsLa
v4l2-ctl produce 1,2,3.jpg
gst-launch-1.0 produce 4,5,6.jpg

Files are deleted? Do you find any violation between your timing and CSI specification?