Failed to Pin Memory & Corrupted Frames on ZED-X with Syslogic Orin

Software C++
,
1

I have a ZED X Camera going into a Syslogic Orin device with a 5 meter GMSL2 cable. I have C++ software using the ZED-SDK and then “polling” the grab function to get the images. I am recording the SVO2 files to disk using the ZED-SDK. I have the ZED X configured at 15 fps with HD1080 resolution.

I am experiencing several data “drop-outs” where the SDK reports it failed to grab the frame, sometimes for over a second: “Corrupted Frame.” I am also seeing several print statements from the software multiple times per second:

Oct 03 22:49:06 vai bash[6416]: [zed_sdk_camera_driver-7] NVMEDIA: Need to set EMC bandwidth : 1436000

Oct 03 22:49:06 vai zed_sdk_camera_driver[6554]: Module_id 56 Severity 2 : failed to pin memory, handle already pinned as read-only

Oct 03 22:49:06 vai zed_sdk_camera_driver[6554]: Module_id 56 Severity 2 : failed to pin memory for NvVIC 13

Oct 03 22:49:06 vai zed_sdk_camera_driver[6554]: Module_id 56 Severity 2 : failed to unpin memory, no such handle being tracked

Oct 03 22:49:06 vai zed_sdk_camera_driver[6554]: Module_id 56 Severity 2 : failed to unpin memory for NvVIC 11

What might the issue be here? Do I need to adjust my EMC Bandwidth on the Orin?

2

Hi @t-byborg
Welcome to the Stereolabs community.

Normally, the ZED SDK outputs Corrupted Frame when the image frames are not good.
Do you have pictures for the image stream to check that?

Could you please also provide details about the software you are using and the ZED X Driver you installed?

We have never seen similar error messages and we are not aware of any zed_sdk_camera_driver that could issue them.

3

The zed_sdk_camera_driver is my C++ application that wraps around the ZED-SDK, calling the grab function periodically. The printout listed in the original post is not directly from my C++ application, so I assumed it was from an underlying library such as the ZED-SDK. I suppose this could be from the Syslogic driver for the ZED-X.

I will set up some specific tests to grab the SVO2 files at the time of the Corrupted Frame errors.

What are the conditions that trigger a Corrupted Frame?

I am using the following versions:

  • L4T: 36.3
  • ZED-SDK: 5.0
  • Syslogic ZED-X driver: syslogic-zedx_1.3.0-L4T36.3.0_arm64.deb
4

Please read more about this in the documentation:

1 Like