RE: 5213 bootloader

Wendi, Mark, Steve,
 
Thank you all for your timely responses. 
 
I didn't think that the RTOS that the application is using made a
difference to a bootloader program so I didn't mention it in my original
email. We are using a MQX RTOS for the MCF5213 known as MQX-lite. Is the
RTOS that the application is using important? I thought once it was
compiled it became part of the S19 file produced by the Code Warrior
compiler. The bootloader I had envisioned would receive the S19 file a
sector at a time thru the serial port, store it in SRAM, and then flash
it into the 5213 flash. Am I oversimplifying what's required?
 
1. the bootloader reads a minimum flash sector size (2k) of the new
application into SRAM through the serial port;
2. it flashes that into the next sector of the 5213 flash. 
3. steps 1 and 2 are repeated until the new application has been fully
received and flashed.
 
The 5213 flash is 256k and my application is above 220k so there isn't
room to keep a copy of the old application stored anywhere in case the
flash of the new application is unsuccessful. Since the hardware design
is fixed and can't be changed, adding an external memory isn't possible.
I realize this isn't the optimum method but I inherited the design and
it's fixed due to safety approvals required by the application.
 
Pat