Lpc2000

Hi Najay

If a download is performed via the Philips FLASH loader (serial) the 
loading program calculates the value and stores it automatically.

If you are using a BDI to load a program, the BDI will probably not 
know that it has to be clever and add this piece of info and will 
probably leave the value at 0xffffffff or 0x00000000 as it is in the 
binary, S-record or whatever it is downloading with.

I don't know the BDI2000 and therefore can not comment about script 
files but there is another solution which I have used in the past.

Add a last step in the tool chain process which takes the 
downloadable image, calculates the necessary value and adds it to 
the image (it is quite easy if working with binary or S-records but 
I haven't done it with ELF for example). Afterwards the BDI can work 
as normal and the code will start since the boot loader believes it 
is a valid program (which is not the case if the unused vector is 
left unmodified)

Regards

Mark Butcher
www.mjbc.ch

--- In lpc2000@yahoogroups.com, "sbechtho" <sbechtho@y...> wrote:
> Is there a way to get this signature at 0x00000014 via BDI2000, 
i.e.
> with help of some script or anything else ?
> 
> Sascha
> 
> --- In lpc2000@yahoogroups.com, Marko Pavlin <mp@h...> wrote:
> > There's signature at 0x00000014.
> > 
> > c/p:
> > This signature is a word-wide number that is stored in the 
unused 
> > location in the ARM7 vector table at 0x00000014. The program 
signature 
> > is the two's compliment of the checksum of the ARM7 vector table.
> > 
> > Marko
> >