I2C timed out error on Jetson Orin Nano DevelopmentKit

[anirudhaduttagupta2004]

Hello everyone,

I’m currently working with a Jetson Orin Nano DevKit and experiencing issues with the USB-C functionality, which I believe are related to I2C communication problems. Specifically, I’m encountering the following error in the kernel logs:

[ 0.232954] i2c_dev: i2c /dev entries driver
[ 3.672348] tegra-i2c 3160000.i2c: Adding to iommu group 1
[ 3.675742] tegra-i2c 3180000.i2c: Adding to iommu group 1
[ 3.679902] tegra-i2c 31b0000.i2c: Adding to iommu group 1
[ 3.685180] tegra-i2c c240000.i2c: Adding to iommu group 1
[ 3.692738] i2c 1-0025: Fixing up cyclic dependency with 3520000.padctl
[ 3.693586] tegra-i2c c250000.i2c: Adding to iommu group 1
[ 3.702137] i2c i2c-2: Added multiplexed i2c bus 9
[ 3.702460] i2c i2c-2: Added multiplexed i2c bus 10
[ 3.702465] i2c-mux-gpio bus@0:cam_i2cmux: 2 port mux on 3180000.i2c adapter
[ 9.575199] tegra-i2c c240000.i2c: I2C transfer timed out
[ 10.980381] imx219 9-0010: imx219_board_setup: error during i2c read probe (-121)
[ 10.996412] imx219 10-0010: imx219_board_setup: error during i2c read probe (-121)
[ 11.395349] tegra-i2c c240000.i2c: I2C transfer timed out

Problem Description:

1. USB-C Driver Chip: I’m using a USB-C controller chip (specifically [fusb301]) that communicates over the I2C bus (I2C1 which is basically i2c@c240000).
2. I2C Detection: Attempts to detect devices on the I2C bus using i2cdetect have not been successful. The detect runs slowly and does not return any devices
3. The I2C on my GPIO header pins also does not seem to work gives the same issue

Troubleshooting Steps Taken:

1. I have tried changing the frequency of I2C using the device tree, although I believe i have successfully changed it, it does not seem to have any effect on the problem
2. Pull up/Pull Down resistor also do not seem to solve the problem

One interesting thing to note is that my USBC works perfectly at the time of flashing, whereas when booted into Tegra Ubuntu, it does not even have power on it.

What steps should i take next? Is it that the bus is somehow physically damaged?

Any help is appreciated thanks in advance!

[WayneWWW]

If this is really the NV devkit, I would suggest you try to flash the pure image from sdkmanager first.

Try both latest rel-35 and rel-36 image.

Also, if possible, swap the module/ carrier board to do cross check if this is specific to one board/module.

Please do not try any other configuration on your side anymore. Just do as what we said.
If this is really NV devkit, highly possible to be a hardware defect that should do RMA.

[anirudhaduttagupta2004]

Hey, so I this is a genuine DevKit, purchased from an authorized retailor.
We sent the Jetson out to the retailor for RMA, however the request was rejected due to “Physical Damage” on the board (the plastic overhead on one of our USB As is damaged, rendering that port useless)
We tried putting on a third party dev kit on the Module, but that also did not seem to solve the issue, the error is still the exact same.
Is it possible that the USB C issue is because of the i2c issue at its core? if so is there any way to check if the actual compute module is damaged?
We have tried reflashing Jetpack 5 and 6 multiple times, without any positive result.
One more thing to note is that there was not underlying “event” that caused this, the jetson just decided to stop working all of a sudden, giving us the i2c error first, followed by the USB C not working