Developing on an MCB2370 eval board, want to get my application to detect/run an updated version of itself.
The original version in always in low memory (0) and an updated version will be flashed at know location in higher flash memory (0x10000 - note that I also build this updated version with a starting ROM address of 0x10000). I have implemeted the logic that allows me to flash the update, so now I have 2 versions of the application programmed. Upon startup (in the reset handler) the original app detects the updated app, then jumps to that app's reset_handler. In essence my original app now behaves as a boot-loader. The updated version copies the vector table to RAM and sets the memory map. All is well, the 'main' of the updated application runs, but as soon as it hits the RTX call os_sys_init, the system goes south. I cannot step through the updated app, I have been 'printf-style' debugging by writing to a memory location to see how far the updated version executed.
Any ideas on what is going wrong or debugging tips?