please also note that, CSI0 D1 and CSI1 D0 P/N will always been swizzled for P/N on Orin Nano.
please use device tree property, lane_polarity to configure a polarity swap on any lane.
Does this swizzle affect both CAM0 (J20) and CAM1 (J21)?
We actually have 2 hardware setups.
One connects the camera via CSI directly. That works.
Second setup connects the camera via GMSL. That does not work.
As the first setup is working there is no general problem with the hardware setup.
Reading the trace log is also seems that the Orin Nano does actually receive data, but I have no access to the documentation of the log messages.
Can you post a link to the documentation of what
tegra-capture-vi err_data , VIFALC_TDSTATE|CHANSEL_FAULT|VIFALC_ACTIONLST … data means or help me with the interpretation of the the attached trace log?
there’s no public documentation for those tracing logs.
please examine the sensor configuration, it should shows camera related signaling, such as SOF,EOF…etc if there’s MIPI data on the CSI channel.
you may visit Jetson Linux 35.4.1 | NVIDIA Developer page to download [Driver Package (BSP) Sources].
please refer to IMX219 device tree as an example, $public_sources/r35.4.1/Linux_for_Tegra/source/public/kernel_src/hardware/nvidia/platform/t23x/p3768/kernel-dts/cvb/tegra234-camera-rbpcv2-imx219.dtsi
re-cap as following.
* lane_polarity
* Based on the camera connector pin.
* CSIx_D0 | CSIx_D1 | CSI(X+1)_D0 | CSI(X+1)CSIx_D1
* LSB | BIT1 | BIT2 | MSB
* if there is a polarity swap on any lane, the bit corrsponding
* to the lane should be set
* e.g. polarity swap on CSIx_D0 only -> lane_polarity = "1"; 0001
* e.g. polarity swap on CSIx_D1 and CSI(X+1)_D0 -> lane_polarity = "6"; 0110
please check your sensor is actually sending frame with 2560x512.
it’s reporting CHANSEL_SHORT_FRAME failure, which means the coming frame height is less than active_h settings.