Sample for NvSci with SIPL

Please provide the following info:
Hardware Platform: DRIVE AGX Xavier™
Software Version: DRIVE Software 10
Host Machine Version: Ubuntu 18.04
SDK Manager Version:


I am trying to setup streaming from SIPL to a consumer through Nvsci.
I am using the Nvidia sample “nvsipl_camera” as a guideline but am experiencing some issues when setting up the output of the ICP and ISP using RegisterImageGroups() and RegisterImages() API calls.

The stream is being setup with 3 packets. The producer attr list is created via GetImageAttributes() API call with ISP output type and the the consumers attr list is created as a NvSciBufType_Image with cpu access required and read only permissions.

The stream is setup and all the element status and packet status events are received by the pool for the 3 packets (each with 1 element).
I am then trying to register the ISP and ICP images using RegisterImageGroups() and RegisterImages() API calls and getting the following error.

: CNvMBufferPool.hpp: 181: GetSciBuffer: Failed to get free buffer from pool
: CNvMBufferPool.hpp: 101: Init: GetSciBuffer failed
: CNvMSensorPipeline.cpp: 214: RegisterImages: ISP[0] buffer pool initialize failed
: CNvMCamera.cpp: 599: RegisterImages: Pipeline register images failed for pipeline:0

How can I debug what exactly is causing this error?

Hi @jaisood,

It looks your are using DRIVE OS and the APIs which you have the problem with aren’t available in the current developer site ( releases.

The forum only targets the support of developer site releases so please contact your nvidia representative to know how to report your issues of non developer site releases correctly. Sorry for any inconvenience!

Hi Vick,

Which APIS are you referring to?

RegisterImages and RegisterImageGroups are available here.

GetImageAttributes is available here:

Those are document pages. isn’t supported via forum. Thanks!

Dear @jaisood,
Could you please file an nvbug and share here to follow up the issue via nvbug

Hi @SivaRamaKrishnaNV

Under what repository should I file the bug? Can you point me to it?