[U-Boot-Users] Question about CFG_ENV_ADDR during RAMBOOT

[Wolfgang Denk]

In message <46535B7B.2090903 at freescale.com> you wrote:
>
> >> Looks to me like it would be better defined:
> >> #define CFG_ENV_SIZE		0x2000
> >> #define CFG_ENV_ADDR		(CFG_MONITOR_BASE - CFG_ENV_SIZE)
> > 
> > No, this is broken as CFG_ENV_SIZE may be (and often actually is)
> > smaller than CFG_ENV_SECT_SIZE
> 
> Why would that matter?  Does the environment need to be located on a sector boundary?

Look at the code.

> > One could argue that a correctly  configured  ramboot  version  would
> > access  the  original  copy  of  the  environment  in flash. But such
> > discussion is void, as ramboot itself it not supported officially.
> 
> My understanding of ramboot is that its sole purpose is to boot U-Boot when flash isn't 
> working at all, so any ramboot-enabled U-Boot would never access anything on flash.

Other people had other ideas.

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
Our business is run on trust.  We trust you will pay in advance.