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.
Several threads in the forum refer to the document but the links are broken and a web search on those words doesn't find the document.
For other readers: the document is about techniques for using a debugger (sw like gdb and hw probe over JTAG or SBW): the steps necessary to reattach the debugger to the target process after LPM4.5. The document is somewhat dated (2009) with terminology for older family members. The example code is also hard to find.
So if you have problems with your LPM4.5 code, you can use these techniques to use a debugger to see exactly what subroutines are getting executed.
For other readers, the app note is 9 years old. The screen captures are out of date.
The "Run" icon in CCS no longer has a pulldown. The place to find "Free Run" is in the Debug perspective, in the "Run" menu.
There is no "Target>Halt". I think now you should choose the "Pause" icon to reconnect the debugger.
When you pause, If everything is OK, you should find the PC to be at the software trap (the infinite loop.) If everything is not OK (the target was never wakened by an interrupt), you should find the PC at the beginning of the boot.c code.
**Attention** This is a public forum