summaryrefslogtreecommitdiff
path: root/drivers
diff options
context:
space:
mode:
authorKyle Moffett <Kyle.D.Moffett@boeing.com>2011-12-15 22:26:52 -0500
committerKumar Gala <galak@kernel.crashing.org>2012-01-11 13:57:53 -0600
commit0ecb55132bcb6292f642657bbbd9b58749b8e303 (patch)
treef4f51a08814a40772e646d4a82d9e09e80d0a68a /drivers
parent7985f7e3ff51ad8024d69a209893f68a2a5d3983 (diff)
downloadu-boot-imx-0ecb55132bcb6292f642657bbbd9b58749b8e303.zip
u-boot-imx-0ecb55132bcb6292f642657bbbd9b58749b8e303.tar.gz
u-boot-imx-0ecb55132bcb6292f642657bbbd9b58749b8e303.tar.bz2
eXMeritus HWW-1U-1A: Add support for the AT24C128N I2C EEPROM
This EEPROM is hardware-write-protected and used to persist key information such as the serial number and MAC addresses even if the primary environment sector in NOR FLASH is overwritten. During manufacturing, the environment is initialized from Linux and then the key parameters copied to the EEPROM via U-Boot: env export -c -s 0x2000 $loadaddr serial# macaddr mac1addr mac2addr eeprom write $loadaddr 0x0000 0x2000 The chip is then locked via hardware for delivery. When doing a field U-Boot upgrade, the environment is erased and reset to the defaults to avoid problems with "hwconfig" changes, etc. After loading the new U-Boot image, the hardware data is reloaded: i2c dev 0 eeprom read $loadaddr 0x0000 0x2000 env import -c $loadaddr 0x2000 saveenv The first three commands are saved in the "restore_eeprom" variable for user convenience. (EG: "run restore_eeprom && saveenv") Signed-off-by: Kyle Moffett <Kyle.D.Moffett@boeing.com> Cc: Andy Fleming <afleming@gmail.com> Signed-off-by: Kumar Gala <galak@kernel.crashing.org>
Diffstat (limited to 'drivers')
0 files changed, 0 insertions, 0 deletions