From mboxrd@z Thu Jan  1 00:00:00 1970
From: Bo Shen <voice.shen@atmel.com>
Date: Sat, 5 Jan 2013 09:53:40 +0800
Subject: [U-Boot] is it possilbe to have uboot find the kernel in the
 file system?
In-Reply-To: <1357349131.22404.44.camel@genx.eng.msli.com>
References: <1357246601.7939.128.camel@genx>
	<20130103210731.AC920200089@gemini.denx.de>
	<1357265217.7939.131.camel@genx>
	<20130104080021.E8EB020008A@gemini.denx.de>
	<1357323597.6335.19.camel@genx.eng.msli.com>
	<20130104221213.2F37A202B9B@gemini.denx.de>
	<1357349131.22404.44.camel@genx.eng.msli.com>
Message-ID: <50E787A4.5010303@atmel.com>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

Hi John Stile,

On 01/05/2013 09:25 AM, John Stile wrote:
>
> 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?

Please check the text base of u-boot for at91sam9g20ek.
If you use the old bootstrap, it jump to 0x23f00000 after reading 
u-boot, while the v2012.10 u-boot use 0x21f00000 as its text base.
If so, you can change u-boot or bootstrap to keep the two address the same.

Best Regards,
Bo Shen

>
>
>
> _______________________________________________
> U-Boot mailing list
> U-Boot at lists.denx.de
> http://lists.denx.de/mailman/listinfo/u-boot