1 # Copyright (c) 2019-2020, NVIDIA CORPORATION. All rights reserved.
3 @page camera_usecase2 Integrating with Custom Board
5 @note SW Release Applicability: This tutorial is applicable to modules in both **NVIDIA DriveWorks** and **NVIDIA DRIVE Software** releases.
7 The camera.gmsl sensor creator supports an additional parameter that you can use to specify a custom board. You describe the board with a JSON file that you pass with a statement such as
9 custom-board-json=/path/to/custom.json
13 dwSensor cameraSensor = DW_NULL_HANDLE;
15 dwSensorParams params;
16 params.protocol = "camera.gmsl";
17 params.parameters = "camera-type=ar0231-rccb, \
18 custom-board-json=/path/to/custom_board.json";
19 dwStatus result = dwSAL_createSensor(&cameraSensor, params, sal);
22 The JSON file contains definitions for the ExtImgDev structs to overwrite the hardcoded one in NVIDIA<sup>®</sup> DriveWorks. If you use the API, you must create camera.gmsl sensor with a correct camera-type that best matches your camera, for example ar0231-rccb-ss3322, however the JSON file can overwrite default settings. A JSON file for ar0231-rccb-ss3322 on Xavier A looks like this:
26 "moduleName" : "ref_max9286_96705_ar0231rccbss3322",
27 "resolution" : "1920x1208",
28 "inputFormat" : "raw12",
29 "interface" : "csi-ab",
33 "serAddr" : [0, 0, 0, 0],
34 "brdcstSensorAddr" : 16,
35 "sensorAddr" : [0, 0, 0, 0],
37 "enableEmbLines" : true,