The Issue of Acquiring Y12 on Orin and Xavier

[xumm_td]

Hello,

Two years ago, we had a project that required us to help a customer retrieve raw data from a MONO sensor on Jetson. To achieve this, after some research, we added a patch to Jetson Linux (as attached), using a custom data format—XY12—to capture the data output directly from the MIPI CSI to memory.

This was successful. According to the TRM, we could obtain the image and simply right-shift the data by 3 bits. See the image below:

However, today I tried to repeat this process on JP6.2@Orin NX and Xavier NX@JP5.1.3, and I found that if I only right-shift by 3 bits, the resulting image data overflows (exceeds 0xFFF). But if I shift by 4 bits instead, the image appears normal.
l4t_36.4.3.patch.txt (8.5 KB)

It seems like the Jetpack upgrade has caused the CSI output format to change from T_R16_I to T_R16, as shown below:

My questions are:

1. Is my assumption correct?
2. If it is, what determines the data format that CSI outputs to memory? I noticed both T_R16_I and T_R16 are supported in the TRM.
3. In the latest Jetpack version, do I still need to apply this patch?

[ShaneCCC]

Suppose this update only for the Xavier and Orin Jetson serials.

[xumm_td]

@ShaneCCC
Hi,
Any updates on this ?

[ShaneCCC]

What’s do you want to clarify.
As my comment the vi5_fops.c for Xavier/Orin use T_R16.