General error queue is out of sync with frame queue

Robotics & Edge Computing Jetson & Embedded Systems Jetson Orin Nano
1

We are working with a mipi Sony imx678 sensor on an 8GB Jetson Orin Nano, Jetpack 5.1.2.
It is streaming as expected both through v4l2-ctl and nvargus.

However we very sporadically get out of sync errors. This can happen after a days or even weeks of continuous stable streaming. Then we typically see this error occur multiple times in a short timeframe.

Nov 14 18:18:13 camco-tegra kernel: [RCE] ERROR: camera-ip/vi5/vi5.c:745 [vi5_handle_eof] "General error queue is out of sync with frame queue. ts=587648548768 sof_ts=587650154304 gerror_code=2 gerror_data=400060 notify_bits=0"
Nov 14 18:18:25 camco-tegra kernel: [RCE] ERROR: camera-ip/vi5/vi5.c:745 [vi5_handle_eof] "General error queue is out of sync with frame queue. ts=599208042944 sof_ts=599289721984 gerror_code=2 gerror_data=400060 notify_bits=40000002
Nov 14 18:18:40 camco-tegra kernel: [RCE] ERROR: camera-ip/vi5/vi5.c:745 [vi5_handle_eof] "General error queue is out of sync with frame queue. ts=614582652768 sof_ts=614584258272 gerror_code=2 gerror_data=400060 notify_bits=0"
Nov 14 18:19:00 camco-tegra kernel: [RCE] ERROR: camera-ip/vi5/vi5.c:745 [vi5_handle_eof] "General error queue is out of sync with frame queue. ts=633786070240 sof_ts=633787675744 gerror_code=2 gerror_data=400060 notify_bits=0"
Nov 14 18:20:09 camco-tegra kernel: [RCE] ERROR: camera-ip/vi5/vi5.c:745 [vi5_handle_eof] "General error queue is out of sync with frame queue. ts=702860874464 sof_ts=702862479968 gerror_code=2 gerror_data=400060 notify_bits=0"
Nov 15 05:33:33 camco-tegra kernel: [RCE] ERROR: camera-ip/vi5/vi5.c:745 [vi5_handle_eof] "General error queue is out of sync with frame queue. ts=41106272817248 sof_ts=41106274422784 gerror_code=2 gerror_data=400060 notify_bits=20000"
Nov 15 05:33:41 camco-tegra kernel: [RCE] ERROR: camera-ip/vi5/vi5.c:745 [vi5_handle_eof] "General error queue is out of sync with frame queue. ts=41113861900768 sof_ts=41113863506304 gerror_code=2 gerror_data=400060 notify_bits=0"

We have seen this happen irrespective of the sensor modes, both 4-lane mipi @60 fps as 2-lane mipi @25fps.

Searching on the nvidia forum, for other people the errors start right away after the streaming start. Hence the new post.

Steps taken so far:

  • Double checked the pix_clk_hz value.
  • CAPTURE_TIMEOUT_MS is at 2500.
  • I boosted the jetson clocks and will reply to this post to notify if it helped.
3

Apply below firmware to try.

4

Thank you for the quick reply.

The update has improved the stability.

Starting from which Jetpack version is this firmware included?

We also noticed that, on a sensor with a lot of stability problems before the patch, we get corrupted images after the firmware upgrade. Most frames are artifact free.
Sadly, I can only share a part of the image, but the artifacts are clear. On the left and right hand sides of the image we see parts of the previous/next frame. Furthermore we see a purple band throughout the image. We also have some images where the purple band is the majority of the frame.

We have not seen this on our other cameras. We will try another sensor mode for this sensor in the meantime.

Frame_artifacts

5

Confirm the raw image from v4l2-ctl.

6

Raw image looks regular. Converted to png through opencv:

v4l2ctl_out
v4l2ctl_out1920×1080 89.6 KB

V4l2-ctl stream is also stable.

7

Please dump the device tree to confirm the badge info if load incorrect ISP configuration.

sudo dtc -I fs -O dts -o extracted_proc.dts /proc/device-tree
9

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.