We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.
The design that I inherited incoporates two hex files. One is a bootloader that is located in the EPROM. The other is an app loaded into external Flash. The code will start in the bootloader and then jump to flash when a timer runs out. EA is not toggled so the external code relies on the interrupt vectors in the bootloader. Therefore, when I use dscope to debug the application I have to load both hex files. I could get this to work in ds51 , but dscope dumps the previous load even though it doesn't use the memory space.
the other thing you can do is create a single startup file that has the interrupt and reset vectors in it, and just link it with your application. This is fairly benign but should give you what you want. We use this technique with our system - we have a ROM bootloader and application in FLASH.