NvSIPL: Configuring CSI2 params

Autonomous Vehicles DRIVE AGX Orin DRIVE AGX Orin General
1

Please provide the following info (tick the boxes after creating this topic):
Software Version
DRIVE OS 6.0.10.0
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 (DRIVE AGX Orin Developer Kit (940-63710-0010-TS5))

SDK Manager Version
2.1.0
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

Issue Description
We have a Drive AGX Orin Dev Kit modified by Nvidia for FPD-Link have successfully ran a serializer patgen test. However, it is unclear how we can configure various CSI2 parameters like frame size, format, data rate, etc. How can we configure this?

The goal is to use an NVSIPL supported device like IMX728 to capture data from a custom CSI2 sensor for prototyping.

Logs
nvidia@tegra-ubuntu:/opt/nvidia/drive-linux/samples/nvmedia/nvsipl/test/camera$ sudo ./nvsipl_camera --platform-config “DS90UB971_RAW12_TPG_DPHY_x4” --link-enable-masks “0x0001 0 0 0” -0 -1 -2 -R -s
DS90UB9724: Revision 1 detected
link 0 is good
DS90UB971: Revision 16 detected!
Enter ‘les’ followed by sensor ID to enable LED
Enter ‘lds’ followed by sensor ID to disable LED
Enter ‘dl’ followed by sensor ID to disable the link
Enter ‘el’ followed by sensor ID to enable the link without module reset
Enter ‘elr’ followed by sensor ID to enable the link with module reset
Enter ‘cm’ to check the module availability
Enter ‘q’ to quit the application

Output
Sensor0_Out0 Frame rate (fps): 29.4989

Output
Sensor0_Out0 Frame rate (fps): 29.9989

Output
Sensor0_Out0 Frame rate (fps): 29.999

Output
Sensor0_Out0 Frame rate (fps): 29.9989

Output
Sensor0_Out0 Frame rate (fps): 29.999

qOutput
Sensor0_Out0 Frame rate (fps): 29.9989

Output
Sensor0_Out0 Frame rate (fps): 29.9989

Sensor0 Frame captured: 419 Frame drops: 0 Frame discontinuities: 0 Frames authenticated: 0 Frames failed to authenticate: 0 Frames authenticated as O0
SUCCESS

3

Dear @j-lee9 ,
Is it like you want to capture frame with a specific resolution, format and a different FPS?

4

Hi Siva,

Actually, I think this thread gives a clearer view of the question. We want to use the nvsipl_camera app with our sensor (connected to DS90UB971 to DS90UB9724). Is it possible for us to develop our own driver, nito, and platform config file? Are there specific resources we can refer to to get started?

Thanks

5

Generally, the camera vendors works with NV camera team to build drivers/NITO files etc and they provide the needed files to bring up the sensor on DRIVE. The driver development is not supported via forum. Please reach out your NVIDIA representative if you need any guidance on this request.

6

Hi Siva,

Thanks for the quick clarification. Before closing this thread, is there another way we can prototype data capture from a custom sensor over FPD-Link to Drive AGX Orin outside of NvSIPL?

7

Is it like you are asking for any other way to capture camera data without using NvSIPL? If so, DRIVE OS does not provide any other way to capture camera data.