Hi TW
Yes, this is correct - I do have a simulation project which allows me to do this.
However I decided not to 'publish' this due to the fact that it is generally not needed by users who usually only change a few set up parameters. Mismatches are quite easy to debug on the hardware by stepping through the first few lines of the routine
fnCheckNewCode(UPLOAD_HEADER *file_header).
The file and its contents are checked there, and if anything doesn't match it returns and starts the original code again.
In order to work with the simulator it requires first simulating the firmware update in the application project and then transferring the simulated memory contents from this project to the boot project. It is not that complicated, but I could imaging (in the worst case) this being more of a challenge to get working than solving the problem on the hardware.
I use this (simulation) method mainly to develop and verify the hardware drivers for the specific devices.
Which compiler and debugger are you using? The latest SP has Keil support but this will not work with the Keil evaluation version due to the fact that it will add a 16k block of zeros - presumable to stop people using the evaluation version for small projects. See also the following:
http://www.luminarymicro.com/component/option,com_joomlaboard/Itemid,/func,view/catid,5/id,2562/#2562Regards
Mark