I2c-2 differences of TX1 hardware revisions

Robotics & Edge Computing Jetson & Embedded Systems Jetson TX1
,
1

Hey,

we’ve recently ran into an issue which seems related to different hardware revisions of the TX1. It concerns the i2c bus 2.
We’ve tested our hardware design for a hardware revision of 699-82180-1000-401 D.0, where we use an additional device with address 0x52 on that i2c bus. This has so far worked well.

However, we have identified an issue now, that seems to be related to different hardware revisions of the TX1. There is a board with revision 699-82180-1000-100 U.0 on which 0x50 0x51 0x52 and 0x53 seem to be taken already.

The documentation only mentions the 0x50 eeprom, which is specified as 256 bytes. Could it be that on this specific hardware revision a 1k-eeprom is used taking all the additional i2c addresses?

Is there any documentation on the different hardware revisions and their differences?

1 Like
4

Hi, can you pls share the photo of these two modules with P/N label? As you can see in faq site: https://developer.nvidia.com/embedded/faq, it is 900-82180-0001-000 in sale.

5

Also, please attach the output of i2cdetect.
we have only one eerpom on 2810 and another on cvb 2197

root@jetson:# i2cdetect 2
Warning: Can’t use SMBus Quick Write command, will skip some addresses
WARNING! This program can confuse your I2C bus, cause data loss and worse!
I will probe file /dev/i2c-2.
I will probe address range 0x03-0x77.
Continue? [Y/n]
0 1 2 3 4 5 6 7 8 9 a b c d e f
00:
10:
20:
30: – – – – – – – –
40:
50: 50 – – – – – – 57 – – – – – – – –
60:
70:
root@jetson:/sys/kernel/debug/clk#

6

image
image2943×2090 1.11 MB

7

This is the output from i2cdetect -r -y 2:

0 1 2 3 4 5 6 7 8 9 a b c d e f
00:     -- -- -- -- -- -- -- -- -- -- -- -- -- 
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
50: 50 51 52 53 -- -- -- -- -- -- -- -- -- -- -- -- 
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
70: -- -- -- -- -- -- -- --
9

There is no update from you for a period, assuming this is not an issue any more.
Hence we are closing this topic. If need further support, please open a new one.
Thanks

have you just purchased the cvm from nvidia?
What is the baseboard you are using? CVB 2597 which nvidia ships as devkit or your custom board?
Why I am asking is, the dump shows that you are not using the CVB from nvidia, Can you run the command with CVB 2597?