NvSIPL Sample Application Error (NvSciBufObjGetAttrList failed)

Please provide the following info (tick the boxes after creating this topic):
Software Version
DRIVE OS 6.0.8.1
DRIVE OS 6.0.6
DRIVE OS 6.0.5
DRIVE OS 6.0.4 (rev. 1)
DRIVE OS 6.0.4 SDK
other

Target Operating System
Linux
QNX
other

Hardware Platform
DRIVE AGX Orin Developer Kit (940-63710-0010-300)
DRIVE AGX Orin Developer Kit (940-63710-0010-200)
DRIVE AGX Orin Developer Kit (940-63710-0010-100)
DRIVE AGX Orin Developer Kit (940-63710-0010-D00)
DRIVE AGX Orin Developer Kit (940-63710-0010-C00)
DRIVE AGX Orin Developer Kit (not sure its number)
other

SDK Manager Version
1.9.3.10904
other

Host Machine Version
native Ubuntu Linux 20.04 Host installed with SDK Manager
native Ubuntu Linux 20.04 Host installed with DRIVE OS Docker Containers
native Ubuntu Linux 18.04 Host installed with DRIVE OS Docker Containers
other

Hi NVIDIA Team,

I am testing out the NvSIPL sample application on the AGX Drive Orin. My current setup involves 2x AR0820 cameras, running on F008A120RM0AV2_CPHY_x4 config. This is the command I used to launch the sample application, and there 2 cameras with 1 stream each from ISP0 running. I do see the displays on my monitor.

sudo ./nvsipl_camera \
    -C --platform-config "F008A120RM0AV2_CPHY_x4" \
    --link-enable-masks "0x0000 0x0000 0x0101 0x0000" \
    --disableISP1Output \
    --disableISP2Output \
    --showEEPROM \
    --nvsci \
    --showfps \
    -d 1 \
    -f "images/test"

I noticed that if I were to try and save the images to disk as well as display, I would get the below error. The function call is from CCompositeHelper.hpp: CUtils::IsRawBuffer. May I know what is triggering this error and how should we go about resolving this? The videos are being saved at a resolution of 960x540 at 30fps which are downsampled by the VIC as defined in the NvSIPL sample application.

Some observations:

  • This error gets triggered consistently and happens within 60 seconds of starting the application.
  • This seems to be not a problem for running only 1 camera even @ 4k resolution at 10 fps.
Output
Sensor8_Out1    Frame rate (fps):               29.9987
Sensor10_Out1   Frame rate (fps):               29.9987

nvsipl_camera: ERROR: NvSciBufObjGetAttrList failed. nvSciStatus: 256

nvsipl_camera: ERROR: PopulateBufAttr failed. status: 10

nvsipl_camera: ERROR: CompositeHelper: CUtils::IsRawBuffer failed for source:41

Output
Sensor8_Out1    Frame rate (fps):               13.4994
Sensor10_Out1   Frame rate (fps):               12.9994

Output
Sensor8_Out1    Frame rate (fps):               0
Sensor10_Out1   Frame rate (fps):               0

Thanks in advance for the help!
Sam

That means, if display(-d <displayID>) is not enabled, the issue is not observed?

Is the above command triggers issue after 60 secs.

Yes, as far as I can tell, running without -d 1 would not trigger the above error. This kind of make sense since the error arises from the Compositor, and when display is not enabled, the Compositor is not created.

Yes, this is the command that I ran which would trigger the above issue. Running with display enabled and >= 2 cameras trying to write file to disk seem to trigger it. Preliminary tests show that enabling display with only 1 camera while writing to disk does not seem to produce this issue.

Let me run it overnight and I will report back.

@SivaRamaKrishnaNV Running for 45 minutes without -d 1 and saving 2 camera streams to disk doesn’t throw the error. Seems to imply that only running the display Compositor with >= 2 cameras while saving the streams to disk leads to that error. Do you have any idea why?

Hi @SivaRamaKrishnaNV any updates on this issue?

Dear @samuel.ongzx,
Our QA has not tested this use case. It could be a bug as well with DRIVE OS 6.0.8.1.
Can you verify the issue with latest release DRIVE OS 6.0.10?

Please try sudo ./nvsipl_camera -c "F008A120RM0AV2_CPHY_x4" -m "0 0 0x0101 0" -1 -2 --showEEPROM --nvsci --showfps -d 1 -f "test2" -r 180

May I know if you have this use case in your application and are blocked with your development or just experimenting?

Hey Siva, sorry for the delayed response! We were just experimenting and found this bug, we do not have a use case currently for displaying and using the buffers at the same time.

When we upgrade to Drive IS 6.0.10, I will give this a shot and report back the results.

Thanks again for clarifying and checking with the team!

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