This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
An application loaded into flash (BASE_ADD 0x00000000) will jump "_c_int00" to symbol (main) correctly in debug or otherwise when CPU reset behave without triggering a fault condition.
When that application base address is set 0x00001000 allowing a 5KB boundary for Boot Loader to exist below the application, the XM4C1294NPCDT fails to find symbol (main) designated in (*_ccs.cmd). The debug secession immediately launches the application into Run mode at the incorrect address. The only way to recover (Run) is by issuing a manual CPU reset where the instruction pointer then jumps to end address 0xFFFFFFFE. Both Tiva & Stellaris BL were set (BASE_ADD 0x00000000) in (*_ccs.cmd). This issue appears to be related to the XM4C processor since both versions of the BL fail to find "_c_int00" symbol pointer to (main).
Moving to a breakpoint set near or on symbol (main) brings the debug secession in to that code offset application address 0x00001000 but debug becomes highly volatile single stepping is unstable crashing ICDI posting "No AET resource can be found"