SIPL Library Source

Robotics & Edge Computing Jetson Systems Jetson Thor
1

HI~!

I’m currently developing a custom sensor driver via SIPL on AGX Thor using the Holoscan SDK with a Holoscan Bridge Board (Lattice-based), and I have a request and some questions regarding the source code availability of libnvsipl.so.

My Setup

  • Platform: AGX Thor

  • SDK: Holoscan SDK

  • Task: Custom SIPL development (writing UDDF for a custom sensor)

  • Hardware: Holoscan Bridge Board (Lattice-based)

Issue / Question

While writing the UDDF for my custom sensor, I noticed that the SIPL library responsible for invoking the functions defined in the UDDF is only provided in binary form:

  • Library path: /usr/lib/aarch64-linux-gnu/nvidia/libnvsipl.so

  • Header file (.hpp) — available ✅

  • Pre-compiled binary (libnvsipl.so) — available ✅

  • Source code — ❌ not provided

Because we only have the header and the compiled binary — without the actual source — it is quite difficult to:

  1. Understand exactly how and when each UDDF-defined function is called internally by libnvsipl.so

  2. Debug unexpected behavior during custom sensor bring-up

  3. Verify whether our UDDF implementation is correctly aligned with what libnvsipl.so expects at runtime

Questions

1. Why is the source code of libnvsipl.so not publicly available? Is this due to IP (Intellectual Property) protection, licensing constraints, third-party dependencies, or some other reason? Understanding the rationale would help us better plan our development approach.

2. Is it possible to make the source code of libnvsipl.so publicly available — either fully or partially? Even a partial release or an open-source version limited to the UDDF call interface layer would significantly reduce the barrier for custom sensor development.

3

Yes, it’s IP concern to public the source code.

Thanks