arunk
December 11, 2020, 12:03pm
1
Hi Team,
@WayneWWW
below snippet is from xavier nx dts (tegra194-p3509-0000-a00.dtsi),
eeprom-manager {
data-size = <0x100>;
bus@0 {
i2c-bus = <&gen1_i2c>;
eeprom@1 {
slave-address = <0x57>;
label = “cvb”;
};
};
bus@1 {
i2c-bus = <&gen2_i2c>;
eeprom@1 {
slave-address = <0x50>;
label = “super-module”;
};
};
};
with i2cdetect tool i could see EEPROM device(0x57) on i2c0. But i couldn’t able to see EEPROM device(0x50) on i2c1. Is EEPROM with slave address 0x50 is present on SoM or carrier board? Please provide your comments on this.
Thanks,
Arun
The i2c0 0x50 is the module eeprom and i2c0 0x57 is the carrier board eeprom.
arunk
December 11, 2020, 12:30pm
3
@WayneWWW
Thank you for clarification, I am able see both 0x50 and 0x57 on i2c0. but is there any other EEPROM on i2c1(gen2_i2c) as defined in the above dts?
as per aliases defined in dts:
gen1_i2c is i2c0
gen2_i2c is i2c1
Hello,
That “super-module” is a NV internal board which also has a eeprom on it. Since you don’t have it, you can just ignore or overwrite this i2c.
1 Like
arunk
December 15, 2020, 12:56pm
6
@WayneWWW
This is from Jetson nano dts(tegra210-porg-eeprom-manager.dtsi)
eeprom-manager {
data-size = <0x100>;
bus@0 {
i2c-bus = <&i2c1>;
word-address-1-byte-slave-addresses = <0x50>;
};
bus@1 {
i2c-bus = <&i2c3>;
word-address-1-byte-slave-addresses = <0x50 0x57>;
};
};
EEPROM with slave address 0x57(i2c3) is present on carrier board. Please let me know where the other 2 EEPROM are present(EEPROM with 0x50 on i2c1 and EEPROM with 0x50 on i2c3) are these present on SoM or carrier board?
This is jetson nx forum board. Please file your issue on nano board if you want to ask questions for nano.
Hi,
What is the purpose of the carrier board EEPROM? Can I custom it layout and store my own data? Thank you!
Please file a new topic and elaborate your issue.