Could you please provide information about the devices represented by I2C addresses 0x50, 0x57, and 0x5f on NVIDIA Jetson Orin Nano

[yhlee1]

Hello,

When examining I2C bus 0 on the NVIDIA Jetson Orin Nano, I’ve come across the addresses 0x50, 0x57, and 0x5f. I’m curious to know what devices or purposes these addresses correspond to. Could you please provide information about the roles of each address and any data associated with them? This information would help me better understand and utilize these devices.

Blockquote
nvidia@ubuntu:~$ 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: 50 – – – – – – 57 – – – – – – – 5f
60:
70:
nvidia@ubuntu:~$ i2cdump -y 0x50
Error: No address specified!
Usage: i2cdump [-f] [-y] [-r first-last] [-a] I2CBUS ADDRESS [MODE [BANK [BANKREG]]]
I2CBUS is an integer or an I2C bus name
ADDRESS is an integer (0x03 - 0x77, or 0x00 - 0x7f if -a is given)
MODE is one of:
b (byte, default)
w (word)
W (word on even register addresses)
s (SMBus block)
i (I2C block)
c (consecutive byte)
Append p for SMBus PEC
nvidia@ubuntu:~$ i2cdump -y 0 0x50
No size specified (using byte-data access)
0 1 2 3 4 5 6 7 8 9 a b c d e f 0123456789abcdef
00: 02 00 fe 00 00 00 00 00 00 00 00 ff 00 00 00 00 ?.?..
10: 00 01 00 01 36 39 39 2d 31 33 37 36 37 2d 30 30 .?.?699-13767-00
20: 30 33 2d 33 30 30 20 4d 2e 32 00 00 00 00 00 00 03-300 M.2…
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 …
40: b0 48 00 00 41 54 d9 2d b0 48 31 34 32 31 31 32 ?H…AT?-?H142112
50: 33 30 30 38 33 31 33 00 00 00 00 00 00 00 00 00 3008313…
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 …
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 …
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 …
90: 00 00 00 00 00 00 4e 56 43 42 00 ff 4d 31 00 00 …NVCB…M1…
a0: 00 00 00 00 00 00 00 00 00 00 00 00 41 54 d9 2d …AT?-
b0: b0 48 01 00 00 00 00 00 00 00 00 00 00 00 00 00 ?H?..
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 …
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 …
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 …
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 4c …L
nvidia@ubuntu:~$ i2cdump -y 0 0x57
No size specified (using byte-data access)
0 1 2 3 4 5 6 7 8 9 a b c d e f 0123456789abcdef
00: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff …
10: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff …
20: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff …
30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff …
40: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff …
50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff …
60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff …
70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff …
80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff …
90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff …
a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff …
b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff …
c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff …
d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff …
e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff …
f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff …
nvidia@ubuntu:~$ i2cdump -y 0 0x5f
No size specified (using byte-data access)
0 1 2 3 4 5 6 7 8 9 a b c d e f 0123456789abcdef
00: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff …
10: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff …
20: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff …
30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff …
40: 13 13 13 13 13 13 13 13 13 13 13 13 13 13 13 13 ???
50: 13 13 13 13 13 13 13 13 13 13 13 13 13 13 13 13 ???
60: 13 13 13 13 13 13 13 13 13 13 13 13 13 13 13 13 ???
70: 13 13 13 13 13 13 13 13 13 13 13 13 13 13 13 13 ???
80: 44 53 41 39 39 38 02 01 d6 03 23 07 08 08 5a a5 DSA998???#???Z?
90: 44 53 41 39 39 38 02 01 d6 03 23 07 08 08 5a a5 DSA998???#???Z?
a0: 44 53 41 39 39 38 02 01 d6 03 23 07 08 08 5a a5 DSA998???#???Z?
b0: 44 53 41 39 39 38 02 01 d6 03 23 07 08 08 5a a5 DSA998???#???Z?
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 …
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 …
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 …
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 …
nvidia@ubuntu:~$

Thank you.

[KevinFFF]

Hi yhlee1,

Are you using the devkit or custom board for Jetson Orin Nano?
What’s your Jetpack version in use?

If you are using the devkit(p3768), there’s the EEPROM using the following I2C address:
0x50 is for the module
0x57 is for the board

Please refer to the following instruction for details in EEPROM.
Jetson EEPROM Layout — Jetson Linux Developer Guide documentation (nvidia.com)

[linuxdev]

Trivia: If you switch bus, then then 0x50 is the i2c of HDMI or DisplayPort’s DDC wire (it is for EDID query of the monitor’s plug-n-play specs; I imagine Obi-Wan Kinobe saying “use the bus Luke”, or “this is not the bus you are after” 😋).