On Sun, 27 Apr 2008 14:01:45 +0200 Stefan Roese sr@denx.de wrote:
On Saturday 26 April 2008, Gary Jennejohn wrote:
+#define CFG_MONITOR_LEN (256 * 1024) /* Reserve 256 kB for Monitor */ +#define CFG_MALLOC_LEN (128 * 1024) /* Reserve 128 kB for malloc() */ +#define CFG_MONITOR_BASE 0xFFF80000
CFG_MONITOR_BASE at 0xfff80000 makes me think that the U-Boot image has a size of 512k. But CFG_MONITOR_LEN is 256k. Which one is correct? I would think that 256k should be enough for this image.
That's a valid point. Actually u-boot.bin is 512kB in length, but only because there's a reset vector at 0xFFFFFFFC. u-boot itself is really only 256kB in size.
So now I wonder - what's correct? If CFG_MONITOR_LEN applies to RAM, which it seems to since it only really affects TOTAL_MALLOC_LEN, then 256kB is correct and no change is required.
I would change the image size to 256k to safe some space in FLASH. For this you have to change TEXT_BASE (in config.mk in your board directory) to 0xfffc0000. And CFG_MONITOR_BASE too. Or even better:
#define CFG_MONITOR_BASE (TEXT_BASE)
Well, I took these values from PPCBoot, as used by the customer, and I see no technical reason to change these values with which the customer is obviously satisfied.
--- Gary Jennejohn ********************************************************************* DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: +49-8142-66989-0 Fax: +49-8142-66989-80 Email: office@denx.de *********************************************************************