I2C Addressing conflicts on Xavier NX

One of our customer reported below issue, can you please help? carrier board is based on Xavier NX devkit board.

The Xavier provides 4 I2C busses, most of which are used for camera control etc. One or 2 of the busses are available to the outside world.

The issue I have is that we have a very busy I2C addressing environment with > 20 devices occupying this space. We already have 2 bus address “shifters” to enable all the head unit addresses to co-exist with the base unit addresses.

Our question is, is there an setting in the driver config that might binds a specific I2C address for the Xavier NX hardware or can we assume that all addresses are available to us?

hello vbhm,

how about using an i2c multiplexer,
you may also check this similar discussion thread for reference, Cam I2C Mux on Jetson Xavier NX in Device Tree - #17 by JerryChang

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.