Excelent .

Did you ever solve your bootloader questions regarding keeping the bootloader in the flash and dealing with the interrupt vectors?

I am facing the same problem. How to manage bootloader with interrupt vector at 0 in flash. Cant we just remove interrupt vector from application and use bootloader interrupt vector?

Why are you guys writing your own bootloader when all the software is provided by Atmel? I don't get it! Thanks for the info!

Thnaks

I know we will be working on a custom bootloader. We need to impement AES 256bit decryption for the bootloader. The firmware will be encrypted with a key specific to the unit serial number. For this the standard Atmel bootloader is no good to us.

rkonjeti,
I am trying to the same thing, we need a custom bootloader as well. I have downloaded my complete application (that runs from 0 on its own) into location 0x1000. now I want on startup at 0 , the image is checked to see if it is valid and then I want to startup the whole application from 0x1000.
Trouble is there are two cstartup.s79 files now, one for the bootloader at 0 and one for the applcation at 0x1000. How can the two exist. Can the application at 0x1000 use the IVECT at 0??
Is there any way to do this??

The normal way to handle something like this is 2 completely separate projects, on for the bootloader and another for the application. The bootloader should be a fully self contained application that runs independantly of the application.

This way when the application space has been erased and is ready for re-programming by the bootloader there is no need for the bootloader to interact, or reply, any of the application routines that are now erased.

Thanks Tschultz for the advice. I have done it in two seperate applications for testing and debugging. However the final product will need to have both the bootloader application and the functional application present. We are allowing for a Wireless transfer of a firmware image via the application to be stored in an external nvram. Then on a reset, the bootloader must check if there is a new image available and write it over the existing one in flash. Then reset again and allow the new functional application to startup.

Hello all,

No reply to this thread from a long time ..?
has any one found the solution ?

I am having the same issue, and stuck there...

I am newbie to Arm and IAR. I have develope an application using IAR5.30 and
AT91SAM7S128 which has interuupt vector starting from 0x0 and rom starting from
0x5000 and when i load this application using jflash utitlity it is working
fine.

On the same configuration(address) i have devloped a bootloader application.Now i want to download first application using this bootloader application. Asthe both bootloader application and the first application has the same interruptvector address 0x0 so when i download it donot work.

Do i need to move the interrupt vector to some where else, ?
When i moved the interrupt vector of my application to 0x5000 , i.e. just in the start of the application, the interrupt are not working.

Kindly send your valuable advise and observation to help solving my problem.

Your kind guidence will be highly appricated


Danii