Jetson Orin Nano i2c error

We have a orin nano module in hand. On the carrier board of DK, pin3 and pin5 external I2C devices cannot get the device address.
A device address of 0x50 is available on other modules.
The following information is about the system.

nvidia@nvidia-desktop:~$ cat /etc/nv_tegra_release
# R35 (release), REVISION: 3.1, GCID: 32827747, BOARD: t186ref, EABI: aarch64, DATE: Sun Mar 19 15:19:21 UTC 2023
nvidia@nvidia-desktop:~$ sudo i2cdetect -r -y 7
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:          -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --
nvidia@nvidia-desktop:~$ i2cdetect -l
i2c-3   i2c             3190000.i2c                             I2C adapter
i2c-10  i2c             i2c-2-mux (chan_id 1)                   I2C adapter
i2c-1   i2c             c240000.i2c                             I2C adapter
i2c-8   i2c             31e0000.i2c                             I2C adapter
i2c-6   i2c             31c0000.i2c                             I2C adapter
i2c-4   i2c             Tegra BPMP I2C adapter                  I2C adapter
i2c-11  i2c             NVIDIA SOC i2c adapter 0                I2C adapter
i2c-2   i2c             3180000.i2c                             I2C adapter
i2c-0   i2c             3160000.i2c                             I2C adapter
i2c-9   i2c             i2c-2-mux (chan_id 0)                   I2C adapter
i2c-7   i2c             c250000.i2c                             I2C adapter
i2c-5   i2c             31b0000.i2c                             I2C adapter

At the same time, the system dmesg has been initializing the relevant information of this i2c interface.

nvidia@nvidia-desktop:~$ sudo dmesg | grep i2c
[    4.319748] i2c /dev entries driver
[    4.323470] tegra-i2c 3160000.i2c: Adding to iommu group 2
[    4.329263] tegra-i2c c240000.i2c: Adding to iommu group 2
[    4.334974] tegra-i2c 3180000.i2c: Adding to iommu group 2
[    4.340652] tegra-i2c 3190000.i2c: Adding to iommu group 2
[    4.346332] tegra-i2c 31b0000.i2c: Adding to iommu group 2
[    4.352033] tegra-i2c 31c0000.i2c: Adding to iommu group 2
[    4.357713] tegra-i2c c250000.i2c: Adding to iommu group 2
[    4.363396] tegra-i2c 31e0000.i2c: Adding to iommu group 2
[    7.004955] i2c i2c-2: Added multiplexed i2c bus 9
[    7.010302] i2c i2c-2: Added multiplexed i2c bus 10
[    7.015334] i2c-mux-gpio cam_i2cmux: 2 port mux on 3180000.i2c adapter
[   13.224174] imx219 9-0010: imx219_board_setup: error during i2c read probe (-121)
[   13.298823] imx219 10-0010: imx219_board_setup: error during i2c read probe (-121)
[ 5684.845100] tegra-i2c c250000.i2c: un-recovered arbitration lost
[ 5684.852101] tegra-i2c c250000.i2c: un-recovered arbitration lost
[ 5684.859019] tegra-i2c c250000.i2c: un-recovered arbitration lost
[ 5684.866162] tegra-i2c c250000.i2c: un-recovered arbitration lost
[ 5684.873070] tegra-i2c c250000.i2c: un-recovered arbitration lost
[ 5684.880620] tegra-i2c c250000.i2c: un-recovered arbitration lost
[ 5684.887403] tegra-i2c c250000.i2c: un-recovered arbitration lost
[ 5684.894323] tegra-i2c c250000.i2c: un-recovered arbitration lost
[ 5684.901001] tegra-i2c c250000.i2c: un-recovered arbitration lost
[ 5684.907655] tegra-i2c c250000.i2c: un-recovered arbitration lost
[ 5684.914299] tegra-i2c c250000.i2c: un-recovered arbitration lost
[ 5684.920961] tegra-i2c c250000.i2c: un-recovered arbitration lost
[ 5684.927606] tegra-i2c c250000.i2c: un-recovered arbitration lost
[ 5684.934268] tegra-i2c c250000.i2c: un-recovered arbitration lost

Is there a good solution for this module?

Can anyone take a look?

Hi chen.xi,
Please follow this topic to check, does bus1 work?

I2C Bus 7 not working on Jetson Orin Nano Developer Kit - Jetson & Embedded Systems / Jetson Orin Nano - NVIDIA Developer Forums

Bus 1 is working.
Access the I2C chip:

root@ubuntu:/home/xrrobot# i2cdetect -y -r 1
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:          -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: UU -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: 50 -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --

Without access to I2C chip:

root@ubuntu:/home/xrrobot# i2cdetect -y -r 1
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:          -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: UU -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --

image
During the test, bus 7 is connected to the I2C chip,

With the latest version of the system, bus 7 is still unable to get the address of the I2C chip on the devkit board.
In addition. The state of bus 1 is normal.

May I ask whether the process of RMA can be used in this case?

Hi chen.xi,

Do you mean that only one module can’t recognize 0x50 on I2C bus 7 and showing the following errors?

[ 5684.845100] tegra-i2c c250000.i2c: un-recovered arbitration lost

Yes, this is the only one I’ve encountered so far.

How is the fail rate in your case?
(i.e. how many modules do you have and found there’s 1 NG module)

Then I would suggest for RMA it.
Jetson FAQ | NVIDIA Developer

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