[U-Boot-Users] Question about CFG_ENV_ADDR during RAMBOOT
timur at freescale.com
Wed May 23 17:58:20 CEST 2007
Wolfgang Denk wrote:
> 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.
Which code? The environment isn't even located in flash, so what difference does it make
if it's not on a sector boundary? There aren't even any sectors!
>> 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.
I don't recall reading any. Can you tell what you're talking about?
Linux Kernel Developer @ Freescale
More information about the U-Boot