On Fri, 2013-01-04 at 23:12 +0100, Wolfgang Denk wrote: > Dear John Stile, > > In message <1357323597.6335.19.ca...@genx.eng.msli.com> you wrote: > > > > > I see the following board configurations supported in current mainline > > > code: at91sam9g20ek_nandflash, at91sam9g20ek_dataflash_cs0, and > > > at91sam9g20ek_dataflash_cs1 . Anything wrong with those? > > > > I'm going to have to wrestle with buildroot's uboot configuration or > > something... But it would be helpful to know what he build error means. > ... > > BR2_TARGET_UBOOT_BOARDNAME="at91sam9g20ek" > > I don't know what "BOARDNAME" is exactly supposed to mean here, but > probably this should be one of the configuration names I listed above. > > ... > > BR2_TARGET_AT91BOOTSTRAP_BOARD="at91sam9g20ek" > > Or this? I have no idea what the difference between BOARDNAME and > BOARD might be... > > > BR2_TARGET_AT91BOOTSTRAP_MEMORY="dataflash" > > OK, it appears you want one of the at91sam9g20ek_dataflash_csX > configurations... > > > make: *** No rule to make target `at91sam9g20ek_config'. Stop. > > Well, as mentioned in my previous message, the known config names are > "at91sam9g20ek_nandflash", "at91sam9g20ek_dataflash_cs0", and > "at91sam9g20ek_dataflash_cs1"; plain "at91sam9g20ek" is NOT a known > config name. > > > What should the target be? > > Depending whether you want to use CS0 or CS1 to address the dataflash > on your board, it should probably be "at91sam9g20ek_dataflash_cs0" > or "at91sam9g20ek_dataflash_cs1". > > > Maybe my buildroot is also so old it doesn't support the new uboot > > configuration syntax? > > I think it's just misconfigured. > > Best regards, > > Wolfgang Denk >
u-boot-2012.10 build does compile with buildroot's .conf settings BR2_TARGET_UBOOT_BOARDNAME="at91sam9g20ek_dataflash_cs1" or BR2_TARGET_UBOOT_BOARDNAME="at91sam9g20ek_nandflash" But after writing my ubootEnvtFileDataFlash.bin to NOR with sam-ba utility (which works with the u-boot-1.3.4), it is not found by the ROM boot loader, so I'm not sure where to go for help. I know ROM boot loader executes what ever it finds at NOR start (0xD0000000) +0x00008400. Does anyone else use a at91sam uboot-2012 and sam-ba, or have any other suggestions? _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot