Hi,
I’m designing carrier board for the Orin Nano, using 2x 4-Lane cameras.
Currently, I’ve used the lane mapping as in the design guide:
Like this:
Technically, by designing the device tree, can any CSI lane be used to any DATA lane for either camera? Namely, can I just route any 4 lanes to each camera? Mix-and-match to CSI lanes?
For example:
Use CSI2_D1_P/N for DATA3 of CAMERA#2?
*** Please note that this reply is generated by LLM automatically ***
To address your question comprehensively, let’s break down the key components and concepts involved in designing a carrier board for the Jetson Orin Nano, particularly focusing on the use of CSI (Camera Serial Interface) lanes and their configuration through the device tree.
CSI Lanes: The Jetson Orin Nano, like other Jetson modules, uses CSI lanes for camera interfaces. These lanes are crucial for transmitting camera data to the module. The Orin Nano has multiple CSI ports, each capable of supporting a certain number of lanes (e.g., CSI 1 x2 lane or CSI 1 x4 lane).
Device Tree Configuration: The device tree is a data structure that describes the hardware components of a system. For the Jetson Orin Nano, the device tree can be configured to manage how CSI lanes are allocated to cameras. This includes defining which CSI lanes are used for which camera and how the lanes are mapped to the camera’s data lines.
The question revolves around the flexibility of allocating CSI lanes to cameras. Specifically, it asks if any CSI lane can be used for any data lane of either camera, allowing for a mix-and-match approach in routing CSI lanes to cameras.
Technical Feasibility: From a technical standpoint, the device tree configuration provides a significant degree of flexibility in how hardware components are utilized. This includes the potential to map CSI lanes to camera data lines in various configurations.
Lane Polarity and Swizzling: However, it’s essential to consider the concept of lane polarity and swizzling. As mentioned by JerryChang, Orin NX/Nano has CSI0 D1 and CSI1 D0 P/N that will always be swizzled for P/N. This means that there are specific constraints on how lanes can be allocated due to the hardware design. The lane_polarity property in the device tree can be used to configure a polarity swap on any lane, which might be necessary depending on the specific lane allocation strategy.
Practical Considerations: While technically possible, mixing and matching CSI lanes to cameras might introduce complexity in terms of signal integrity, electromagnetic interference (EMI), and potentially impact the overall system performance. It’s crucial to ensure that any custom lane allocation does not violate the electrical or signal integrity specifications of the Jetson Orin Nano or the cameras.
In conclusion, while the device tree configuration offers flexibility in allocating CSI lanes to cameras, it’s not entirely a matter of simply routing any 4 lanes to each camera without consideration for the underlying hardware constraints. Factors such as lane polarity, swizzling, and potential signal integrity issues must be carefully evaluated. For a custom carrier board design using 2x 4-lane cameras with the Jetson Orin Nano, it’s advisable to:
In summary, while there is flexibility in configuring CSI lanes, a thorough understanding of the hardware and careful planning are necessary to ensure a successful and reliable design.
*** Please give the thumbs up if you get answers you like. Or provide feedback to help us improve the answer. ***
This is a very long, AI-generated answer.
However, it doesn’t answer my simple question - is it possible to use any CSI2 lane for any DATA lane in one of my 2x 4-lane cameras?
hello matan.hershkovitz,
1st 4-lane should be using CSI0 clock and CSI0/1 data.
2nd 4-lane should be using CSI2 clock and CSI2/3 data.
you may also check Jetson Orin NX Series and Orin Nano Series Design Guide for [Table 10-3. CSI Configurations].
Thank you
