IMX728 on CSI‑C fails to start with sample_camera (no deserializer detected / sipl status 10)

Summary

We are evaluating IMX728 cameras with the DriveWorks SDK on DRIVE Thor using the sample_camera application on DriveOS 7.0.3.

When the camera is connected to the CSI-C interface, sample_camera fails during initialization with either of the following errors:


DW_INVALID_ARGUMENT: CameraMaster: no deserializer detected, cannot initialize NvSIPL.

or


DW_UNEXPECTED_EVENT: CameraMaster::resume failed with sipl status 10

However, with the same hardware setup, nvsipl_camera works correctly and displays video as expected.

We understand that the camera module we are currently using does not exactly match an officially supported NVIDIA camera configuration.

  • Officially supported camera: BF8S103G-100-00

  • Camera currently in use: BF8S103G-100-01

Even with that limitation in mind, we would like to confirm whether CSI-C is expected to work with IMX728 in the DriveWorks SDK, and if so, what the correct configuration should be.

Environment

  • Platform: NVIDIA DRIVE Thor (P3960)

  • Software:

  • DRIVE OS 7.0.3

  • DriveWorks SDK 7.0.3

  • Camera configuration: Smartlead BF8S103G-100-01

  • Connection:

  • Interface: CSI-C

  • 4 x IMX728 cameras connected

Application Used

We tested the DriveWorks sample_camera sample located under:


/usr/local/driveworks/samples/src/sensors/camera/camera

Rig Parameter Configuration

The following parameter string was used in the rig file:


camera-name=R0SIM728S3RU2120NB2,

interface=csi-c,

deserializer=MAX96792A_Fusa_nv,

disable-custintf=1,

skip-eeprom=1,

CPHY-mode=1,

link=0,

output-format=raw+processed,

async-record=1,

file-buffer-size=16777216,

format=mp4,

nito-file=/usr/share/camera/R0SIM728S3RU2120NB2.nito

Rig file used:


rig_IMX728x1.json

Observed Error in sample_camera

When we run sample_camera with the above configuration, we get the following error:


[26-04-2026 23:46:51] Driveworks exception thrown: DW_INVALID_ARGUMENT: CameraMaster: no deserializer detected, cannot initialize NvSIPL.

Related log file:


CSI-C_link=0_Faile.txt

Verification with nvsipl_camera

Using the same hardware configuration, we confirmed that the camera works correctly with nvsipl_camera and video is displayed as expected.

Command used:


./nvsipl_camera \

--platform-config "R0SIM728S3RU2120NB2_5Des_CPHY_x2" \

--link-enable-masks "0x0000 0x11 0x0000 0x0000 0x0000" \

--showfps -d 1

Behavior When the Deserializer Parameter Is Removed

If we remove the following parameter from the rig:


deserializer=MAX96792A_Fusa_nv

DriveWorks then fails with the following log:


[26-04-2026 23:55:58] CameraMaster: master init failed with status = 10

[26-04-2026 23:55:58] Driveworks exception thrown: DW_UNEXPECTED_EVENT: CameraMaster::resume failed with sipl status 10

Related log file:


CSI-C_link=0_Faile__no_deserializer.txt

Status on Other CSI Interfaces

Based on the deserializer names documented here:

we confirmed that IMX728 works correctly with the DriveWorks SDK on the following interfaces:

  • CSI-GH

  • CSI-EF

  • CSI-D

  • CSI-AB

The issue occurs only when using CSI-C.

Questions

  1. Is CSI-C supported for IMX728 when using the DriveWorks SDK on DRIVE Thor?

  2. If CSI-C is supported, what is the correct deserializer name or rig configuration for this interface?

  3. Is it expected that nvsipl_camera works, while DriveWorks sample_camera fails with SIPL status 10?

  4. If CSI-C can be used with IMX728 in the DriveWorks SDK, are there any additional requirements or platform-config constraints that must be satisfied?

CSI-C_link=0_Faile__no_deserializer.txt|attachment (25.5 KB)
rig_IMX728x1.json.txt (1.2 KB)
CSI-C_link=0_Faile.txt|attachment (8.8 KB)

Let me check on this and get back to you.

Dear @Natsuha_Shishido ,
Could you connect camera on csi-ab, csi-c port and run nvsipl_camera with verbose flag and share nvsipl_camera and syslog for both cases?

Dear @SivaRamaKrishnaNV

csi-ab

./nvsipl_camera --platform-config “R0SIM728S3RU2120NB2_5Des_CPHY_x4” --link-enable-masks “0x1111 0x00 0x0000 0x0000 0x0000” --showfps -d 1 -v 4

csi-c

./nvsipl_camera --platform-config “R0SIM728S3RU2120NB2_5Des_CPHY_x2” --link-enable-masks “0x0000 0x11 0x0000 0x0000 0x0000” --showfps -d 1 -v 4

IMX728__csi-ab__link=0-3 -v 4.log|attachment (1.2 MB)
IMX728__csi-c__link=0-1 -v 4.log|attachment (689.7 KB)

Could you please share the /var/log/syslog for both cases. Clear the syslog file before running each command to ensure only application related info is logged.

Dear @SivaRamaKrishnaNV
Understood.
I got the log again.

IMX728__csi-c__link=0-1 -v 4 1.log|attachment (689.7 KB)
syslog_csi-ab.txt (530.2 KB)
syslog_csi-c.txt (311.3 KB)
IMX728__csi-ab__link=0-3 -v 4 1.log|attachment (1.2 MB)

Dear @Natsuha_Shishido ,
Could you try with deserializer=MAX96792A in gmsl parameters. I notice deserializer value as MAX96792A when dumping platform configuration in /var/log/syslog with nvsipl_camera in verbose mode . CSI-C supports only 2 IMX728 cameras .

Dear @Natsuha_Shishido ,
Did you get chance to test? Could you please provide any feedback here?

Dear @SivaRamaKrishnaNV

I’m back from vacation.
i will try.

Dear @SivaRamaKrishnaNV
Adding deserializer=MAX96792A as a parameter, it worked properly. thank you very much.