On Thu, Jun 26, 2003 at 08:50:27AM +0200, Wolfgang Denk wrote:
In message 20030624235953.GA16810@zumanetworks.com you wrote:
I don't know who designed it that way (because I don't care about the FADS board), but according to "board/fads/u-boot.lds" the environment on this board is aligned on a 256kB boundary _after_ the U-Boot image. So MONITOR_LENGTH must not include the environment, and ENV_IS_EMBEDDED shall not be set.
In which case NOTHING in environment.c is compiled, and "environment" goes unresolved....
unresolved, meaning:
ld -Bstatic -T /home/nyet/src/local/u-boot/board/fads/u-boot.lds -Ttext 0x02800000 -n cpu/mpc8xx/start.o \ --start-group board/fads/libfads.a cpu/mpc8xx/libmpc8xx.a lib_ppc/libppc.a fs/jffs2/libjffs2.a fs/fdos/libfdos.a net/libnet.a disk/libdisk.a rtc/librtc.a dtt/libdtt.a drivers/libdrivers.a post/libpost.a post/cpu/libcpu.a common/libcommon.a lib_generic/libgeneric.a --end-group \ -Map u-boot.map -o u-boot cpu/mpc8xx/start.o(.got2+0x24):/local/nyet-build/u-boot-mrv/cpu/mpc8xx/start.S:99: undefined reference to `environment' make: *** [u-boot] Error 1
But this is normal for a non-embedded environment. If you don;t embed it with the U-Boot image it will not be initialized after installing the image anyway (because it is not included), so there is little sense initializing it at compile time.
There are several other options: in cases where the environment is directly adjecent to the U-Boot image (it looks as if the FADS is such a configuration) you can "include" the environment, producing a bigger image which then contains an initialized environment.
It is up for the board maintainer to decide what he wants.
Best regards,
Wolfgang Denk
-- Software Engineering: Embedded and Realtime Systems, Embedded Linux Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de All I ask is a chance to prove that money can't make me happy.