关于Camera bringup的文档

关于Csi_trace的使用,以前参考的以下连接:

https://elinux.org/Jetson/l4t/Camera_BringUp

这部分文档适用于Orin 系统吗?有没有跟新或者更完整的文档,我并没有找到tag:VIFALC_ACTIONLST tag:CHANSEL_PXL_SOF tag:ATOMP_FE tag:VIFALC_TDSTATE等等经常出现的tag的定义,这对我解读csi-trace 造成了很大的困扰。
csi_trace4.txt (166.7 KB)
如果有,麻烦告知最新连接地址,谢谢。

hello 541449841,

that eLinux external page is out-of-dated.
however, here’re failures regrading to your packets.

 tag:CHANSEL_PXL_SOF channel:0x23 frame:10 vi_tstamp:24833022424192 data:0x0000000000000001
 tag:CHANSEL_NOMATCH channel:0xe0 frame:10 vi_tstamp:24833022438496 data:0x0000000000000569
 tag:CHANSEL_SHORT_FRAME channel:0x20 frame:10 vi_tstamp:24833036142176 data:0x0c00200001000000

CHANSEL_SHORT_FRAME occurred by your coming signaling is less than expectation.
please examine your sensor configuration, especially the active_h settings in the device tree,
furthermore, you may see-also developer guide, Sensor Software Driver Programming for development.

Hi,Jerry
谢谢答复,我知道问题出在哪里,我们真实的需求是想要知道MIPI RX 上的一些具体信息,目前在sensor 的driver 开发和bringup 是没有问题的,但是当接入我们新的产品时,遇到无法点亮的情况,我们显得有些不知所措。(由于是新研发的产品,sensor输出的MIPI信号可能不是完全正确的)作为CMOS sensor 设计厂商,我们迫切需求Orin 的MIPI RX接收器能准确反映出sensor 输出的MIPI信号存在的问题。
目前我所了解到的是csi_trace log 可以清楚的反映出这些信息,但是对于我们来说,解读是很困难的,这给我们带来了不小的困扰。
所以目前有没有更新的文档可以release给我们?

或者说,看到CHANSEL_SHORT_FRAME这个tag,怎么判断是H方向的像素点多了还是少了,还是W方向的像素点多了还是少了?MIPI RX实际接收到像素点是多少W X H

hello 541449841,

there’re line length and frame height settings from sensor side usually.
line stands for horizontal direction (active_w), and frame for vertical direction (active_h).

you may also check AGX Orin TRM, please refer to [2.2 CHANSEL]->[2.2.2 Notifications]
for instance,

SHORT_FRAME is emitted when a FE (i.e. Frame End) appears from NVCSI before the normal number of pixels has appeared.

please see-also Topic 280696.