According to the latest JetPack doc in here.

A Jetson system has two EEPROMs, one on the module and one on the carrier board. But in this repo. We can only read/write the eeprom on the jetson module.

So do you have a plan to support read/write the eeprom on the carrier board?

Looking forward to your reply~

Thanks for this very handy program. I want to use it to write to the EEPROM and I've configured my kernel with CONFIG_AT24=m. I've looked through the dts files and I'm uncertain about the changes I should make to enable the driver. Would it be possible to add an example in the README.md of the device tree changes necessary to enable it?

I'm using a TX2 NX (soc type 186) for what it's worth, which I believe has the EEPROM on i2c bus 7 at address 0x50.

Thanks

Hi,

we've an issue with a single Jetson Nano SoM: The mender update failed.

Usually, for our SoM's, the TNSPEC (generated by tegra_boardspec()) looks like this:
3448-400-0002-F.0-..., but with the problematic SoM the TNSPEC looks like this: 3448-401-0002-F.0-.... According to Part number is 699-8bbbb-ssss-fff RRR the change was been made within the FAB entry: From 400 to 401.

But, according to Jetson Module EEPROM Layout, the entry identified as FAB is in the Jetson EEPROM layout the version entry. Here is the code snippet from tegra_boardspec():

return snprintf(buf, bufsiz,
			"%-4.4s-%-3.3s-%-4.4s-%s-1-%u",
			&eeprom.partnumber[5],
			&eeprom.partnumber[15],
			&eeprom.partnumber[10],
			boardrev,
			(soctype == TEGRA_SOCTYPE_194 ? 2 : 0));

The FAB entry of the TNSPEC is made out of the version entry of the partnumber.

So, the question is whether FAB and the version entry of the partnumber is same or is this a mistake or is this by intention?

I couldn't find more information regarding the meaning of FAB.

Can anyone give me a hint?

Thanks.