> 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?
Yeah, i use the "--uboot boneblack_flasher" flag in my setup-card.sh creator script to grab the "blank eeprom" u-boot, vs the normal am335x_evm build. #BeagleBone & BeagleBone Black ABI2:am335x_evm:SPL http://rcn-ee.net/deb/tools/am335x_evm/MLO-am335x_evm-v2014.07-rc3-r8 ABI2:am335x_evm:BOOT http://rcn-ee.net/deb/tools/am335x_evm/u-boot-am335x_evm-v2014.07-rc3-r8.img #BeagleBone Black (eeprom) ABI2:am335x_boneblack:SPL http://rcn-ee.net/deb/tools/am335x_boneblack/MLO-am335x_boneblack-v2014.07-rc3-r8 ABI2:am335x_boneblack:BOOT http://rcn-ee.net/deb/tools/am335x_boneblack/u-boot-am335x_boneblack-v2014.07-rc3-r8.img > 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? Correct.. For devices programmed at the factory, users should only use the 1st patch. https://github.com/RobertCNelson/Bootloader-Builder/blob/master/patches/v2014.07-rc3/0001-am335x_evm-uEnv.txt-bootz-n-fixes.patch This is also located under /opt/source/ of the production image. It contains a few tweaks for where we have the kernel boot files located in the debian image. Along with a poor man's cape manager checker.. However, the second patch really should only be used by oem's who are flashing the bbb, as it assumes 1Ghz, the black's ldo setting etc. https://github.com/RobertCNelson/Bootloader-Builder/blob/master/patches/v2014.07-rc3/0002-NFM-Production-eeprom-assume-device-is-BeagleBone-Bl.patch >>> 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. Well, when i set this up originally, we didn't have much for a clone market. So we definitely need to look at this again. I just didn't want people running this image on clones that did have the 1Ghz or the black's ldo setup. I need to think, what's still safe for a blank bbw.. 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.
