On Tue, Jul 1, 2014 at 1:06 PM, Robert Nelson <[email protected]> wrote: > On Tue, Jul 1, 2014 at 11:51 AM, Jason Kridner <[email protected]> wrote: >> On Tue, Jul 1, 2014 at 11:49 AM, Víctor MV <[email protected]> wrote: >>> Jason >>> >>> I'm searching for one of the old BB images that allowed to write the EEPROM >>> from u-boot. One of those that you could use to access the u-boot even if >>> the EEPROM was empty. >> >> You don't have to go old for that. Robert continues to build updated >> u-boot images that ignore the EEPROM such that you can boot and >> program it. Realize there is a test-point on the board if you want to >> un-write-protect the EEPROM. >> >> The image-builder specifies the image to get here: >> https://github.com/beagleboard/image-builder/blob/master/tools/setup_sdcard.sh#L1220 >> >> That means that the actual built u-boot images are at >> http://rcn-ee.net/deb/tools/am335x_boneblack/. >> >> I'm not sure where the sources are! Robert, please jump in here as it >> isn't obvious, especially since the image build script doesn't have an >> option for rebuilding the bootloader (it seems it should). > > Well, i really don't have a script to build "one" bootloader. ;) > > https://github.com/RobertCNelson/Bootloader-Builder > > I kinda ended up in a situation where i'm tracking 15 boards in u-boot > mainline. ;) opps! > > As u-boot releases happen, i push those patches to " > https://github.com/eewiki/u-boot-patches/ " so we can hard link to > them. The patches in Bootloader-Builder tend to churn a lot.
This is all fine, but it should be clear what is going on to someone visiting http://beagleboard.org/source. Perhaps I just missed it. > >> I see a bunch of patches here: >> https://github.com/eewiki/u-boot-patches/blob/master/v2014.07-rc3/0001-am335x_evm-uEnv.txt-bootz-n-fixes.patch >> (per >> http://eewiki.net/display/linuxonarm/BeagleBone+Black#BeagleBoneBlack-Bootloader:U-Boot), >> but I don't see the one for am335x-boneblack.h. > > Oh, I'm just ignoring the fact u-boot has a "am335x-boneblack" config, > as "am335x-evm" supports both beaglebone's... Easier to share a > microSD between the white/black. OK, so where you use it in setup-card.sh is simply a hack to give a different URL to fetch it? You are using this patch (https://github.com/RobertCNelson/Bootloader-Builder/blob/master/patches/v2014.07-rc3/0002-NFM-Production-eeprom-assume-device-is-BeagleBone-Bl.patch) and then building normally for am335x-evm? > >> Robert?!? >> >> I believe we should push the am335x-boneblack.h file into mainline and >> annotate it clearly to be used only in cases of a board without an >> EEPROM. > > The Seems like you hesitated here. Perhaps we could #include <am335x-evm.h> and then overwrite some settings and add a clear note that this is for ignoring that EEPROM? The reasons are that lots of people look for boneblack in the u-boot sources (without success), lots of people try to build clones without EEPROMs and struggle to figure out how, and out-of-tree patches are always hard to locate with confidence they are used in the build of the software at hand. > >> >>> >>> I've been trying with some of the images available at >>> http://downloads.angstrom-distribution.org/demo/beaglebone/archive/. >>> But i keep getting something like: >>> >>> U-Boot SPL 2011.09-00000-gf63b270-dirty (Nov 20 2011 - 19:58:24) >>> Texas Instruments Revision detection unimplemented >>> Incorrect magic number in EEPROM >>> read_eeprom() failure >>> : 0 >>> spl: fat register err - -1 >>> ### ERROR ### Please RESET the board ### >>> >>> or >>> >>> U-Boot SPL 2011.09-00010-g81c8c79 (Feb 13 2012 - 14:48:03) >>> Texas Instruments Revision detection unimplemented >>> Incorrect magic number in EEPROM >>> read_eeprom() failure >>> : 0 >>> mmc_read_data: timedout waiting for status! >>> mmc_send_cmd: timedout waiting for cmddis! >>> ** Can't read partition table on 25000000:0 ** >>> ** Partition 1 not valid on device 25000000 ** >>> spl: fat register err - -1 >>> ### ERROR ### Please RESET the board ### >>> >>> and doesn't allow me to actually access u-boot prompt to write the magic >>> number. >>> >>> Do you happen to have one of those images around (i believe that the right >>> u-boot.img would be enough)? > > GND test point TP4 and boot with: > > http://rcn-ee.net/deb/testing/2014-05-14/BBB-blank-eMMC-flasher-debian-7.5-2014-05-14-2gb.img.xz > > as long as your i2c bus works, this'll boot and program the eeprom.. > > Regards, > > -- > Robert Nelson > http://www.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.
