I am checking the operation of the camera input on the MIPI I/F with trace logging enabled.
I am referring to the Jetson/l4t/Camera BringUp (Jetson/l4t/Camera BringUp - eLinux.org).
There are six questions I would like to ask.
-
I understand that the information output in the trace log can tell us if there are connection errors or malfunctions in the camera communication, is this correct?
-
Is there a way to determine whether an error is resolved or unresolved from the information output in the trace log?
-
Is there a document that describes what each value (CHANSEL_NOMATCH, CSIMUX_STREAM, etc.) output to “tag” means as a keyword?
Is there a document that describes the format of “data” in “tag” as well?
4.It’s same “tag” in rtcpu_vinotify_event and rtcpu_vinotify_error.
Is there a difference in normality and abnormality between event and error with the same “tag”?
rtcpu_vinotify_error: tstamp:30979959918 cch:-1 vi:0 tag:CSIMUX_FRAME channel:0x01 frame:0 vi_tstamp:991358572448 data:0x00000000000000a4
rtcpu_vinotify_event: tstamp:30980458431 cch:-1 vi:0 tag:CSIMUX_FRAME channel:0x01 frame:0 vi_tstamp:991358572448 data:0x00000000000000a4
5.If multiple cameras are connected, is it possible to identify which camera device the error information output to the trace log comes from?
Can the “cch” or “vi” number information be used to identify the camera?
6.Is there any way to detect camera communication connection errors other than detecting errors from the trace log?
target: Orin AGX
OS : Ubuntu20.04 L4T
Jetpack:5.1.2
Best regards