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 was just wondering how or if it is possible to communicate with the MAX96712 (and eventually the linked sensor in a running camera module). For example - when there is no sample application running, i2cdetect detects a device at address 0x29 (deserializer), but write will fail using i2cset. When a sample application with camera is attached i2cset -y -f 0 0x29 0x00 0x0d i
(the device id) will work fine, but trying to read the bytes back using i2cget give ‘device busy’
Alternatively, I see character devices at /dev - for example /dev/cdi-dev.0.29
which I assume is bus 0, address 29. Can we talk to devices through that?
Otherwise, how does one use i2ctools to probe registers of connected devices - or is this even possible? Thanks!