Platform Camera Configuration
NVIDIA DRIVE® OS Safety build enforces authentication of all camera modules that are enabled in platform camera topology configuration. There is no option to disable the authentication step in a Safety build. DRIVE OS SIPL core refuses an application request to start a camera streaming for any module whose authentication cannot be successfully finished for whatever reason:
- SIPL device driver for a sensor does not support authentication
- Physical camera module does not support authentication
- Physical camera module is not provisioned with required key materials
- Authentication is supported, but fails during session establishment for any reason
For more information, refer to Understanding the Sensor Input Processing Library (SIPL) Framework
isAuthEnabled
flag set to true
in a platform
config. Following is an example SIPL database JSON file description of the IMX728
module:{
"cameraModules": [
{
"name": "V1SIM728S2RU2030NB20",
"description": "IMX728 RGGB module - 30FOV - MIPI-IMX728, MAX96717",
"serializer": {
"name": "MAX96717F"
},
"sensors": [
{
"name": "IMX728",
"i2cAddress": "0x1C",
"isAuthEnabled" : true,
"virtualChannels" : [
{
"cfa": "rggb",
"width": 3840,
"height": 2160
}
]
}
],
"eeproms": [
{
"name": "M24C04",
"i2cAddress": "0x54"
}
]
}
]
}
Platform integrators can enable authentication individually for each camera module in SIPL platform configuration for non-safety or debug builds. For more information, refer to Adding a Sensor Configuration