Please provide the following info (tick the boxes after creating this topic): Software Version
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
SDK Manager Version
1.9.3.10904
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
Hello,
I’d like to get the DriveWorks SDK Reference: Camera Sample (nvidia.com) running - this sample should be already be cross-compiled to aarch64 and located on the target.
However I use a custom camera with a MAX96717F and an IMX623 (the configurations of both are available). So, my understanding is that I …
… have to configure the camera (serializer and imager) via the GMSL backward channel - means, I need a I2C connection from Orin to the Drive AGX integrated deserializer (MAX96712?)
… have to configure the rig-file of sample_camera and get it running resp. get frsames or images from my camera
Could you pls. confirm my assumed workflow and could you please tell me where to find a description how to get I2C access the the internal deserialzer. Also would be helpful to know, whether the deserializer is already configured?
Hello SivaRamaKrishnaNV,
no it isn’t and I have seen in other posts, that NV often refers to camera vendor. Since the camera is from Continental, I already have the configs fro the imager and the serializer. Therefore I need to know how to download these configs to the camera. As I meantion, my approach would be via I2C from Orin to internal deserializer to GMLS into camera.
Dear @DominikS,
Unfortunately such custom camera bring up related issues can not be supported via forum and may need seperate engagement. Please reach out to your NV representative for this issue for further guidance.
Ok, I understand. But could you tell me how the deserializer is configured by default? For instance, is the internal deserializer configured by booting up the Drive OS?
Hello @SivaRamaKrishnaNV and NV-team,
is there any desciption about I2C for the Drive OS are Drive Works SDK? It would be helpful to know where commands like i2cdetect -y -r -3 are described.
Linux commands like i2cdetect are not specific to the DRIVE OS or DriveWorks SDK but are part of the underlying Linux operating system utilities for managing I2C buses and devices. As such, documentation for these commands is usually found in general Linux resources rather than specific to the DRIVE platform.
Could you please provide more context or details about why you’re inquiring about this specific command?
Hello @VickNV, the reason behind is the usage of a custom camera (from Continental). In the SDK Reference I have seen some forwarding till DriveWorks SDK Reference: Camera (nvidia.com). Anywhere here I actually expected where/how to send the configuration (registers) for the serializer (MAX96717) and for the camera imager (IMX623). Could you please tell me, where to find such a command, library, etc.?
Or is it possible that something do not excist because all suggested cameras are populated with an internal EEPROM, which have all necessary settings inside by default?
