Please provide the following info (check/uncheck the boxes after clicking “+ Create Topic”): Software Version
DRIVE OS Linux 5.2.0
DRIVE OS Linux 5.2.0 and DriveWorks 3.5
NVIDIA DRIVE™ Software 10.0 (Linux)
NVIDIA DRIVE™ Software 9.0 (Linux)
other DRIVE OS version
other
Hi Thank you for reply.
Yes, I could find the libnv_eeprom.so in targetfs on host (5.2.0 SDK).
But it is not present in target file system, could be due to that i have flashed DRIVE SOFTWARE 10.0 and 5.2.0 both? If I flash only 5.2.0 SDK the target is not booting and stuck on blank screen after flash. Please let me know if I can only flash 5.2.0 SDK and mitigate the booting problem.
Thank you
Hi Thank you for checking, After following the above steps, I can ssh to target and run the nvsipl app. However We are facing the failure in cameras chipID read (below msg). Note this is based on Ar0234 camera and we have obtained the driver from the camera vendor. Please let me know any inputs. Thank you
Hi Thank you for the support.
We have reached to camera vendor and seems the I2C address are expected to work. Since the sensor read is failing, we are suspecting we are missing the powering on for sensor? do we need to power on the camera explicitly ? Do you suggest any i2c probing tool on Drive platform? Thank you
What package did your camera vendor provide you for the AR0234 Leopard Imaging camera module?
Is it for DRIVE OS 5.2.0 or DRIVE Software 10.0?
The camera module isn’t supported per DRIVE Ecosystem - Hardware and Software | NVIDIA Developer and I assume it works on DRIVE AGX platform on your camera vendor’s side so you should clarify the problem with them.