Hello,
I’m using a Jetson Orin Nano Developer Kit with JetPack 6.2 (L4T 36.4.3) and have encountered an unexpected issue with the I²C bus numbering.
🛠️ Issue Description
According to 'Jetson Orin Nano Developer Kit Carrier Board Specification’ , pins 3 and 5 (I2C1_SDA & I2C1_SCL) on the 40pins expansion header should be assigned to /dev/i2c-1
while pin 27 and 28 should be assigned to i2c-0.
However, after a fresh JetPack installation, these pins are now assigned to /dev/i2c-7
instead of /dev/i2c-1
while pin 27 and 28 is assigned to i2c-1.
I have confirmed this by running ls /dev/i2c-*
and i2cdetect -y 7
, which detects my connected device correctly.
🧪 Steps Taken to Troubleshoot
-
Flashed JetPack 6.2 using SDK Manager (Clean installation)
-
Checked device tree mappings (
/proc/device-tree/aliases/i2c*
) →/dev/i2c-7
is mapped toc250000.i2c
, while/dev/i2c-1
is mapped toc240000.i2c
. -
Verified I²C pinmux settings (
/sys/kernel/debug/pinctrl/.../pinmux-pins | grep -i i2c
) → No issues detected. -
Performed “Reset Settings in NVIDIA Configuration” in UEFI** → No change in behavior.
❓ Questions
- Has NVIDIA officially changed the I²C bus numbering in JetPack 6.2?
- If not, what could be causing this remapping?
- Is there a way to restore the default I²C bus mapping (
/dev/i2c-1
for pins 3,5) without manually altering the device tree?
This behavior is unexpected, and I haven’t found any relevant discussions regarding this issue.
If this is an intentional change in JetPack 6.2, I would appreciate any official confirmation or documentation regarding this update.
Thanks in advance for your help!