[U-Boot] FSBBP: uboot Programming on to the flash for MPC8548 for bootup

[Ajeesh Kumar]

Hi Andy,

Thank you for your Info, so if my compiled output is <200k, my .bin file
will easily fit into the boundary?

Regards,
   AJEESH KUMAR


-----Original Message-----
From: Andy Fleming [mailto:afleming at gmail.com] 
Sent: Tuesday, September 09, 2008 3:16 AM
To: ajeesh at tataelxsi.co.in
Cc: u-boot at lists.denx.de
Subject: Re: [U-Boot] FSBBP: uboot Programming on to the flash for MPC8548
for bootup

On Wed, Aug 27, 2008 at 12:16 AM, Ajeesh Kumar <ajeesh at tataelxsi.co.in>
wrote:
> hi sir/madam,
>
> I'm using a MPC8548E processor(power pc) also, i've interfaced a nor 
> flash of 128 MB to the processor.
> i've read few documents and got to know that the uboot.bin should be 
> programmed at 0xfff80000.
> Also, when i saw the uboot.bin size it was 512K. so, it could fit 
> between 0xfff80000 - 0xffffffff.
> I 'M USING ABATRON BDI2000/BDI3000 FOR THIS.
> Now my question is:
> 1) If i'm making changes(addition/deletion of code) to the 
> bootloader(uboot
> 1.2) and re compile it, i believe that the size of the uboot.bin will 
> get changed i.e >/< 512K. NOW AT WHICH LOCATION I SHOULD FLASH THE 
> UBOOT.BIN(SIZE IS NOT EQUAL TO 512) FOR Eg.  If my uboot.bin size is 
> >512K ?????


Well, it's not likely you will change the size of the binary.  You see, the
512K size is a result of a quirk of the 85xx platform.  The reset vector is
at 0xfffffffc, but we define the base address to be 0xfff80000, so we fill
in the space between, and it's 512K.

The result is, you don't need to mind the size, unless you grow the compiled
output by over 200K.  Try to avoid that ;)

Andy


The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments contained in it.