On Tue, Sep 8, 2015 at 4:59 PM, Phil Mills <phil.mi...@gmail.com> wrote: > Gerald, > > Robert's given me a workable answer to my question already, so I'm set, BUT > it seems like a pretty heavy-weight option - totally suitable for > manufacturing / mass-production / other "blank slate" scenarios, but very > heavy for Joe User who's just accidentally typed "i2cset -y 1 -0x50...." > with a paperclip in the wrong spot and corrupted the EEPROM on his BBB that > he's spend the last month working on. > > > > Your "I2C writes is what we do" response seems to imply that you've got a > lighter-weight method to edit contents on the EEPROM than what RCN's > described? > > If so, I'd really appreciate a description of how YOU get to an unbootable > BBB to a state where you can write to a blank/corrupted EEPROM.
CircuitCo actually has two stages. First they run my "usbflasher" on all boards to set the initial eeprom.. Next all boards go thru a "tester" which adds the unique serial number in eeprom, along with a 100% functionality test.. 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 beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
