I would like to know what is the purpose of having CSI0_D0_N/P and CSI0_D1_N/P signals on the camera #0 connector (J20) of Orin Nano Devkit seeing that one cannot use them either in 2-lane mode or in 4-lane mode together with the CSI1_D0_N/P and CSI1_D1_N/P because of the missing of CSI0_CLK_N/P, please ?
The J20 on devkit carrier can only support x2 lane sensor as you can see below note in P3768_A04 schematic:
Note:
x4 camera support in current software only works with the lower clock lane of the x4 clock interface.
This means that CSI0_CLK or CSI2_CLK are supported for x4 configurations, but not CSI1_CLK or CSI3_CLK.
Since J20 has CSI1_CLK, only a x2 camera interface is supported.
J21 which uses CSI2_CLK can support both x2 or x4 camera interfaces.
x4 camera support in current software only works with the lower clock lane of the x4 clock interface.
Would there be any future evolution in the software to have x4 camera working with the higher clock lane of the x4 clock interface (i.e. CSI1_CLK_N/P of the J20) ? Otherwise, I find CSI0_D0_N/P and CSI0_D1_N/P signals currently useless on the J20 port. Or am I wrong ?
That’s only on devkit carrier as J20 only has CSI1_CLK. For custom design, there is no issue if customer follow below design in the Design Guide, which means x4 mode is supported with CSI0_CLK + CSI0_D0/1 + CSI1_D0/1.
Thank you. I was asking about the Jetson Orin Nano Devkit, there’s been certain initial confusion btw the available MIPI-CSI2 channel on the J20 when designing and adapting the device-tree for the adapter board to custom camera modules.