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. -phil On Tuesday, September 8, 2015 at 3:35:32 PM UTC-6, Gerald wrote: > > I2C writes is what we do. > > Gerald > > > On Tue, Sep 8, 2015 at 4:32 PM, Phil Mills <phil....@gmail.com > <javascript:>> wrote: > >> Gerald, >> >> I've got the SRM and know the format of the data that needs to get >> written there - I'm just stuck on HOW to get it there: >> >> Could anyone provide* a good set of instructions for getting access to a >>> uBoot prompt* from a stock flasher image OR provide current* links to >>> the blank-EEPROM manufacturing images* (or equivalents) that RCN's >>> referenced? >>> >> >> The two methods I've seen discussed on the forums are: >> 1) Manually updating the EEPROM from i2c commands issued within uBoot >> 2) Using a flasher image with a uBoot build that bypasses the >> magic-number-check and writes content to the EEPROM from a command-line >> script. >> >> >> >> >> On Tuesday, September 8, 2015 at 3:19:29 PM UTC-6, Gerald wrote: >>> >>> Take a real BBB and copy the contents if you need to. EEPROM data varies >>> with serial number and revision data. But the EEPROM data is described in >>> the SRM, is still valid and is not stale or old. >>> >>> Gerald >>> >>> >>> On Tue, Sep 8, 2015 at 4:15 PM, Phil Mills <phil....@gmail.com> wrote: >>> >>>> I have inherited responsibility for a bunch of 3rd-party direct clones >>>> of a Beaglebone Black C5 (only known change is in silkscreening). >>>> >>>> Since none of these have any contents written to the onboard EEPROM, >>>> they fail to boot with "CCCCC" written to the serial console with no uSD >>>> card, and >>>> >>>> >>>>> U-Boot SPL 2015.01-00001-gb2412df (Jan 29 2015 - 15:01:06) >>>>> Incorrect magic number (0xffffffff) in EEPROM >>>>> Could not get board ID. >>>>> Incorrect magic number (0xffffffff) in EEPROM >>>>> Could not get board ID. >>>>> Unknown board, cannot configure pinmux.### ERROR ### Please RESET the >>>>> board ### >>>> >>>> >>>> ...written to the console when I try to boot it from a uSD cards with a >>>> stock BBB image (the 2015-03-01 Debian 7.8 image). So clearly I need to >>>> get some good contents into the EEPROM. >>>> >>>> >>>> I've been trying to hunt down instructions for how to access the U-Boot >>>> prompt to manually write the EEPROM via the i2c bus, but haven't hit any >>>> luck there. >>>> >>>> >>>> Robert Nelson's posted links in the past to what he's described as the >>>> "factory images for flashing boards with blank EEPROMs", but those links >>>> (to rcn-ee.org) are stale/dead or behind apparently access-controlled >>>> folders on his server. >>>> >>>> >>>> >>>> Could anyone provide a good set of instructions for getting access to a >>>> uBoot prompt from a stock flasher image OR provide current links to the >>>> blank-EEPROM manufacturing images (or equivalents) that RCN's referenced? >>>> >>>> -- >>>> 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...@googlegroups.com. >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>> >>> >>> >>> -- >>> Gerald >>> >>> ger...@beagleboard.org >>> http://beagleboard.org/ >>> >> -- >> 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...@googlegroups.com <javascript:>. >> For more options, visit https://groups.google.com/d/optout. >> > > > > -- > Gerald > > ger...@beagleboard.org <javascript:> > http://beagleboard.org/ > -- 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.
