Hi Patrick, Ensure you modify config.h after running the clean and configure steps before compiling, otherwise it will re-copy the default configuration file.
Only once you have compiled with the correct config file should the u-boot image be copied over. BTW there is a run-time config file for u-boot that can be used to achieve the same effect (i.e. without the need to rebuild and copy over u-boot) - this might be worth investigating as a lower-risk option. Cheers, Andrew. On 16 January 2015 at 11:20, Patrick Schmidt <[email protected]> wrote: > Mikkel, > > I just found this forum after a couple beaglebones I have starting > displaying the same problem discussed here. I figured I would reply to you > since I saw you just posted. I have a question on how to implement Andrew's > solution. I am able to download and build the u-boot, everything is working > fine there. Then I have two files, MLO and u-boot.img that I can copy into > the boot directory (/boot/uboot I am using Debian and booting from the > eMMC). My question is when are we suppose to edit the config.h file? After > I build and move the 2 files? I'm wondering because in Andrew's post he > mentions that he edited the config.h file then rebuilt the u-boot. But when > I try this it just overwrites the config.h file back to the original. So I > assume the process should be first download and build the u-boot, then move > the MLO and u-boot.img to the boot directory, finally edit the config.h > file. Is this correct? I have tried everything I can think of but my board > is still hanging on boots about 1 out of 20. Forgive me because I am not > too familiar with Debian. Thank you for any help you can provide! > > On Thursday, January 15, 2015 at 8:43:07 AM UTC-6, Mikkel Kirkgaard > Nielsen wrote: >> >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> Hi there Martin. >> >> On 2015-01-14 18:05, [email protected] wrote: >> > Just as a +1 to Andrew's findings: In summary, this software fix is >> > still highly useful. >> >> Glad you were able to solve your issue. >> I'm just wondering if Andrew's autoboot solution/hack hasn't >> propagated to the official software yet? >> >> Seems odd if not, since so many has been bitten by it and it is now 15 >> months since it was first described (2013-10-28: >> https://groups.google.com/forum/#!msg/beagleboard/ >> aXv6An1xfqI/2_tLa7oWQBIJ). >> >> >> I haven't studied the u-boot source before but I just took a sniff at >> the mainline repository (http://git.denx.de/u-boot.git). >> I found that for BBB (really am335x) u-boot still defaults to aborting >> autoboot if any characters are received on the serial console and then >> waiting forever for further commands. >> >> Below is a patch mitigating this situation in mainline master >> (binaries at >> http://www.mikini.dk/wp-content/uploads/2015/01/u- >> boot_mainline_BBB-autoboot-patch_201501151.zip). >> It requires typing more characters ("stop") to abort and uses a new(?) >> config feature to reset the board if autoboot is aborted but no >> commands are entered (for 30 sec). >> Except for the 30 sec timeout, which doesn't kick in for some unknown >> reason, it seems to behave ok. >> >> Disclaimer: this is mostly an experiment, there is a lot of u-boot >> trees and patches floating around for the BBB (like >> https://github.com/beagleboard/u-boot), so probably mainline hasn't >> got the most recent stuff for BBB yet. >> >> >> diff --git a/include/configs/ti_am335x_common.h >> b/include/configs/ti_am335x_common.h >> index 5ed86d9..c58f467 100644 >> - --- a/include/configs/ti_am335x_common.h >> +++ b/include/configs/ti_am335x_common.h >> @@ -12,6 +12,12 @@ >> #ifndef __CONFIG_TI_AM335X_COMMON_H__ >> #define __CONFIG_TI_AM335X_COMMON_H__ >> >> +#define CONFIG_AUTOBOOT_KEYED >> +#define CONFIG_AUTOBOOT_STOP_STR "stop" >> +#define CONFIG_AUTOBOOT_PROMPT "autoboot in %d seconds (type '%s' to >> abort)\n",bootdelay,CONFIG_AUTOBOOT_STOP_STR >> +#define CONFIG_BOOT_RETRY_TIME 30 >> +#define CONFIG_RESET_TO_RETRY >> + >> #define CONFIG_AM33XX >> #define CONFIG_ARCH_CPU_INIT >> #define CONFIG_SYS_CACHELINE_SIZE 64 >> @@ -102,4 +108,7 @@ >> /* Now bring in the rest of the common code. */ >> #include <configs/ti_armv7_common.h> >> >> +#undef CONFIG_BOOTDELAY >> +#define CONFIG_BOOTDELAY 5 >> + >> #endif /* __CONFIG_TI_AM335X_COMMON_H__ */ >> >> >> > Thank you Andrew and Guglielmo for your work! >> >> Thumbs up, also for Guillermo ;). >> >> - -- >> Mikkel >> ,= ,-_-. =. >> ((_/)o o(\_)) >> `-'(. .)`-' >> \_/ >> keybase.io/mikini >> -----BEGIN PGP SIGNATURE----- >> Version: GnuPG v1 >> >> iQEcBAEBAgAGBQJUt9HnAAoJEJ2luFWzaTSaqCoH/2cuFepOVkHGM0gGaGV5U8Dg >> /Z3O4Cb1zGyasSeYLZbU5XfOms6k66hbLmbQiDYIKkMv/KS0gcjjkuFaZBE2NdVJ >> xFnaPS/XPd8MJcwWQMVScFafNJE1E4KLHe437FeenPZLEBcgtZc/AsTFX+mybKhC >> oQfaUmrA9gT2KGmFoGB8Sp+4q4reciXicHRfet78aEF8g9FdqprQvf4xjfcZYgxL >> 0cNNbXh+mmT+AjSCB4CEze25V5yitvfT744WUUHFznfRWXkRVvKpiVeiDwdswKcs >> AaV5yjCqxb0F3iM4leRxdDy3FhuMjxmyZxk9HpwO/sLKExigNktpd3aRjuHO7ds= >> =jU44 >> -----END PGP SIGNATURE----- >> > -- > For more options, visit http://beagleboard.org/discuss > --- > You received this message because you are subscribed to a topic in the > Google Groups "BeagleBoard" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/beagleboard/aXv6An1xfqI/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- 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.
