hang on ... can u-boot binary extend beyond CONFIG_ENV_ADDR?

hang on ... can u-boot binary extend beyond CONFIG_ENV_ADDR?

[Robert P. J. Day]

  ok, one last dumb question before i throw caution to the winds. i'm
looking at the u-boot board defn file for this board,
include/configs/MPC8315ERDB.h, and i see the following in there:

  #if !defined(CONFIG_SYS_RAMBOOT)
        #define CONFIG_ENV_IS_IN_FLASH  1
        #define CONFIG_ENV_ADDR         \
                        (CONFIG_SYS_MONITOR_BASE + CONFIG_SYS_MONITOR_LEN)

i followed all that through, and CONFIG_ENV_ADDR ends up being defined
by:

#define CONFIG_SYS_MONITOR_LEN  (384 * 1024) /* Reserve 384 kB for Mon */

but the u-boot.bin file created via meta-yocto-bsp is larger than
that:

-rwxr-xr-x. 2 rpjday rpjday   423964 Jul  5 06:46
	u-boot-mpc8315e-rdb-v2016.03+gitAUTOINC+df61a74e68-r0.bin

  does that make sense? how can the u-boot binary overlap where the
persistent environment is supposed to live?

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================