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.

Source of Data Abort

Other Parts Discussed in Thread: CODECOMPOSER

Hi,

debugging with CodeComposer and XDS100v2 USB Emulator ( using Windows7 and Starterware) the programme repeatedly runs into an infinite loop that belongs to FIQHandler/AbortHandler/UndefInstHandler.


Does CodeComposer provide a mechanism to detect the source of such an exception?
For instance at what address a data abort exception has been caused?
Thank you.

Regards,
Martin