On Wed, Apr 8, 2015 at 10:44 AM, Robert P. J. Day <[email protected]> wrote: > On Wed, 8 Apr 2015, Robert Nelson wrote: > >> U-Boot# i2c md 0x50 0x0c.2 >> 000c: 30 30 30 43 32 34 31 34 42 42 42 4b 30 31 30 33 000C2414BBBK0103 > > and just to clarify an earlier curiosity of mine, is it true that > u-boot's "eeprom" command has no relevance here? i've never used that > command but it seems that BBB EEPROM access must be done exclusively > via i2c, correct?
Well, it is wired up: 204 #define CONFIG_CMD_EEPROM 205 #define CONFIG_ENV_EEPROM_IS_ON_I2C 206 #define CONFIG_SYS_I2C_EEPROM_ADDR 0x50 /* Main EEPROM */ 207 #define CONFIG_SYS_I2C_EEPROM_ADDR_LEN 2 208 #define CONFIG_SYS_I2C_MULTI_EEPROMS and looking at: http://lists.denx.de/pipermail/u-boot/2007-September/025043.html The i2c md command is just more useful.... Regards, -- Robert Nelson https://rcn-ee.com/ -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
