I2C issue with jetson Nnao

Autonomous Machines Jetson & Embedded Systems Jetson Nano
1

Jetson nano for AGV, 5 devices connected via i2c to nano, initially working fine now when I do the i2cdetect -y on either of the 2 busses it freezes and doesn’t display any device. with no devices attached it loads instantly and displays correctly that no devices are detected. I replaced the jetson module, then replaced with a second carrier board and 3rd module with the error still persisting. works fine with a pi4. Any advice would be appreciated. I imagine if I buy a 4th nano the problem may persist, I am considering trying a Orin Nano but I’m unsure if this may have the same i2c issues.

20240306_165323
20240306_1653231800×4000 619 KB

3

There are two bus on the Nano header. Both -y 0 and -y 1 have problem?

4

Yes, I initially thought it might have been a fault with only the one bus but unfortunately I am experiencing faults on both bus’

5

What’s the BSP version?
Any slave device connected?

nvidia@tegra-ubuntu:~$ sudo i2cdetect -y 0
[sudo] password for nvidia:
Warning: Can't use SMBus Quick Write command, will skip some addresses
     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@tegra-ubuntu:~$ sudo i2cdetect -y 1
Warning: Can't use SMBus Quick Write command, will skip some addresses
     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@tegra-ubuntu:~$ cat /etc/nv_tegra_release
# R32 (release), REVISION: 7.3, GCID: 31982016, BOARD: t210ref, EABI: aarch64, DATE: Tue Nov 22 17:30:08 UTC 2022
6

We see the same output with i2cdetect -y, we have to use de option ‘-r’ to correctly see the connected devices:

root@localhost:~# i2cdetect -y 0
Warning: Can't use SMBus Quick Write command, will skip some addresses
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:
10:
20:
30: -- -- -- -- -- -- -- --
40:
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60:
70:
root@localhost:~# i2cdetect -r -y 0
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:          -- -- -- -- -- -- UU -- UU UU -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- UU -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --
7

Sorry for the late response.
Is this still an issue to support? Any result can be shared?

8

To clarify previous comments I was using i2cdetect -r -y 0 and i2cdetect -r -y 1

things I tried

  • Replacing carrier board with genuine carrier board
    -Replacing carrier board with seed studio carrier board
    -loaded a clean image onto the jetson
    -i tried 6 different i2c devices worked fine with other SBC and the subsequent replacement but not the original
  • When I received the new jetson that fixed the issue I then removed the module and replaced with the old one and used the same MicroSD card and the issue returned which makes me believe it is in fact an issue with the jetson nano

I have 5 jetsons and 2 have i2c buss errors on bus 1 . The new Jetson Nano has fixed the issue for now but if it happens on this board I will be replacing with Orin. Fortunately Amazon replaces them within 12 months of purchase.

10

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