-----Original Message----- From: u-boot-bounces@lists.denx.de [mailto:u-boot-bounces@lists.denx.de] On Behalf Of Wood Scott-B07421 Sent: Thursday, January 20, 2011 1:28 AM To: chrisv@cyberswitching.com Cc: u-boot@lists.denx.de Subject: Re: [U-Boot] environmental "baudrate" not used at boot up
On Tue, 18 Jan 2011 21:34:45 -0800 chrisv@cyberswitching.com wrote:
On Sun, Jan 16, 2011 at 06:01:22AM -0800, chrisv@cyberswitching.com
wrote:
... Any advice on where to take it from here?
Hi everyone,
I investigated this a little further, and I'm wondering if the problem is related to the initialization ordering in lib_arm/board.c.
Here's the sequence:
start_armboot():
- init_baudrate() -> getenv_r() -> serial_setbrg()
- env_relocate()
Note that init_baudrate() calls getenv_r("baudrate") and passes either the result (on success) or CONFIG_BAUDRATE (on error) to serial_setbrg(). Only after this does the environment get relocated using env_relocate().
The full NAND code only works after relocation. So you cannot read out the NAND environment, in the normal way, before serial init -- you get the default environment instead.
If you are booting from NAND, I suggest using CONFIG_NAND_ENV_DST to have the NAND SPL load the environment at the same time as it loads U-Boot. If you're using some preloader other than U-Boot's NAND SPL, you'll need to see if it supports something similar.
Hello Scott
Is this feature available/tested on any FSL platform. The code you pointed to does not seem to be used by FSL platforms.
It would be good idea to pull this in for P1/P2 RDB nand boot loader.
Regards Poonam
-Scott
U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot