On Mon, Nov 4, 2013 at 2:05 PM, joem <joem@martindale-electric.co.uk> wrote:
: yes.  my concerns here are that the EEPROM would be overwritten by
:user applications otherwise, potentially destroying the ability of CPU
:Cards to identify the device.

I2C eeproms dirt cheap - have two eeproms - one user data (such as calibration data
for instruments, keys, etc) and one for system data.

_______________________________________________
arm-netbook mailing list arm-netbook@lists.phcomp.co.uk
http://lists.phcomp.co.uk/mailman/listinfo/arm-netbook
Send large attachments to arm-netbook@files.phcomp.co.uk

Given the need for device-tree info, and RID, etc etc, presumably, how large of an EEPROM would we technically need?

The Most recent revision MEBs have a 64K EEPROM, perhaps we could split the single eeprom memory into two segments? 

--
Christopher Thomas
Firemoth Industries, LLC - Owner
christopher@firemothindustries.com
214-458-5990