here’s developer guide for Pinmux Changes.
may I know what your actual pin connections? if your carrier board schematic differs from that of the reference carrier board in Jetson Xavier NX Developer Kit. you must change the pinmux configuration applied by the software.
please see-also reference driver to register your i2c device.
pinmux spreadsheet is used to create the board configuration, it’s the cfg file for default pin settings. those settings may be alter by device tree, or driver pin control operations.
please check the public release sources,
for example, $public_sources/Linux_for_Tegra/source/public/hardware/nvidia/soc/t19x/kernel-dts/tegra194-soc/tegra194-soc-i2c.dtsi
did you meant you’ve device connected to gen1_i2c: i2c@3160000?
you should update the device tree. please add your device property within the scope of i2c@3160000.
note, you should double check you’ve assign regulator settings correctly. otherwise you might see i2c communication failure.
please refer to Jetson Xavier NX Product Design Guide for the [Figure 12-1. I2C Connections].
it’s actually using signal DP_AUX_CH3_P and DP_AUX_CH3_N.
so, it is… signal (I2C1) <—> TRM (I2C9) <—> DTS/ Dev (i2c-8, i2c@31e0000).