Just make sure you ground the Write Protect pin on the EEPROM. Gerald
On Tue, Sep 8, 2015 at 4:38 PM, Phil Mills <[email protected]> wrote: > Robert, > > Thanks for the prompt (and detailed!) reply. That's exactly the > information I'm trying to find. > > ...now I just have to convince our IT staff / McAffee to white-list your > web server (if it ain't one thing, it's another) so I can get those files. > > This may be useful information to add to a wiki somewhere - I can't be the > only person with blank (or inadvertently borked) BBB EEPROMs running > around. > > -phil > > On Tuesday, September 8, 2015 at 3:30:18 PM UTC-6, RobertCNelson wrote: > >> On Tue, Sep 8, 2015 at 4:15 PM, Phil Mills <[email protected]> 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? >> >> So the "blank-flasher" (did everything by default) went away. Instead >> we now have a "usbflasher".. >> >> Step 1: (microSD) >> >> >> http://rcn-ee.com/rootfs/bb.org/testing/2015-09-06/usbflasher/BBB-blank-debian-8.1-usbflasher-armhf-2015-09-06-2gb.bmap >> >> http://rcn-ee.com/rootfs/bb.org/testing/2015-09-06/usbflasher/BBB-blank-debian-8.1-usbflasher-armhf-2015-09-06-2gb.img.xz >> >> (bmaptools 3.2) >> sudo bmaptools copy --bmap *.bmap *.img.xz /dev/sdX >> >> Step 2: (usb drive) >> Format it as fat32, 2 or 3 files "custom: job.txt" and the image files.. >> >> For example: >> >> to flash: 2015-03-01 >> >> First download the base image: >> >> >> http://rcn-ee.com/rootfs/bb.org/release/2015-03-01/lxde-4gb/bone-debian-7.8-lxde-4gb-armhf-2015-03-01-4gb.img.xz >> >> Then the "eeprom" >> >> >> https://raw.githubusercontent.com/RobertCNelson/boot-scripts/master/device/bone/bbb-eeprom.dump >> >> finally crate the "job.txt" file >> >> abi=aaa >> conf_eeprom_file=bbb-eeprom.dump >> conf_eeprom_compare=335 >> conf_image=bone-debian-7.8-lxde-4gb-armhf-2015-03-01-4gb.img.xz >> conf_resize=enable >> conf_partition1_startmb=1 >> conf_partition1_fstype=0xE >> conf_partition1_endmb=96 >> conf_partition2_fstype=0x83 >> conf_root_partition=2 >> >> Step 3: (flashing) >> >> Insert "microSD" with usbflasher image bmap'ed to it.. >> Insert "usb flash drive" with >> bone-debian-7.8-lxde-4gb-armhf-2015-03-01-4gb.img.xz, bbb-eeprom.dump >> & job.txt all in the base directory >> GND TP4 (write protect on eeprom) >> Power board >> >> Serial Log the first one to make sure it correctly flashes.. >> >> 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. > -- Gerald [email protected] 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
