In the camera application depicted in the diagram, we utilize GMSL for transmitting images to the SOC.
When using the AGX Orin platform with JetPack 6.0, occasionally encountering the “err_data = 512” error when attempting to open RGB, where each frame capture reports this error.
Hello,
Thanks for visiting the NVIDIA Developer forums! Your topic will be best served in the Jetson category.
I will move this post over for visibility.
Cheers,
Tom
Increase below in vi5_fops.c to try.
#define CAPTURE_TIMEOUT_MS 2500
Please also get the trace log to check.
vi5_fops.c has added define CAPTURE_TIMEOUT_MS 2500 .
This is the syslog where the issue occurred。
The on = 1 in the log for stream G2XX rgb 10-0066 indicates that it is enabled. on = 0 indicates that it is disabled.
syslog.txt (637.6 KB)
I mean increase the timeout like 5000.
Get the trace log.
ok,I try to increase the timeout and get a trace log
I attempted to change the timeout to 10000, but the RGB report still occasionally shows the error ‘err_data = 512’.
Trace log as follows
syslog.txt (1.2 MB)
Enable the trace log by below command.
echo 1 > /sys/kernel/debug/tracing/tracing_on
echo 30720 > /sys/kernel/debug/tracing/buffer_size_kb
echo 1 > /sys/kernel/debug/tracing/events/tegra_rtcpu/enable
echo 1 > /sys/kernel/debug/tracing/events/freertos/enable
echo 3 > /sys/kernel/debug/camrtc/log-level
echo 1 > /sys/kernel/debug/tracing/events/camera_common/enable
echo > /sys/kernel/debug/tracing/trace
cat /sys/kernel/debug/tracing/trace
Trace log as follows，Please analyze it, thank you.
trace.zip (1.4 MB)
The short frame error tell the output size doesn’t as driver reported.
kworker/3:3-139 [003] .... 7056.680176: rtcpu_vinotify_event: tstamp:221286364907 cch:-1 vi:0 tag:CHANSEL_SHORT_FRAME channel:0xc1 frame:0 vi_tstamp:7081154912192 data:0x0000200001000000
Can you tell me what this log means?
rtcpu_vinotify_error: tstamp:223926929327 cch:-1 vi:0 tag:CSIMUX_STREAM channel:0x00 frame:3 vi_tstamp:7165661714080 data:0x0000000000000001
The error tell the un-supported SPURIOUS data. Could be un-supported user define type data like below.
Table 1. MIPI Data Type IDs Supported by CX3
| Data Type ID | Name |
|---|---|
| 0x00 | Frame Start Code |
| 0x01 | Frame End Code |
| 0x12 | Embedded 8-bit non-Image Data |
| 0x1E | YUV422 8-bit |
| 0x22 | RGB565 |
| 0x23 | RGB666 |
| 0x24 | RGB888 |
| 0x2A | RAW8 |
| 0x2B | RAW10 |
| 0x2C | RAW12 |
| 0x2D | RAW14 |
| 0x30 | User Defined 8-bit Data Type 1 |
| 0x31 | User Defined 8-bit Data Type 2 |
| 0x32 | User Defined 8-bit Data Type 3 |
| 0x33 | User Defined 8-bit Data Type 4 |
| 0x34 | User Defined 8-bit Data Type 5 |
| 0x35 | User Defined 8-bit Data Type 6 |
| 0x36 | User Defined 8-bit Data Type 7 |
| 0x37 | User Defined 8-bit Data Type 8 |
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.