Part Number: TM4C1294NCZAD
Tool/software: Code Composer Studio
The problem described in thread "CCS/DK-TM4C129X: No AET resource", also started by me, has recurred, this time on a custom target, but also using the TM4C1294NCZAD. This time, however, executing
eval("DEBUG_DumpBreakpoints()")
does not make the problem go away.
I found that, after setting and clearing breakpoints at C$$EXIT and C$$EXITE, it was possible to set a breakpoint a few source lines above the original breakpoint line. It must be that the "AET" message is popped up when there is some kind of difficulty in setting a breakpoint at a particular instruction. It may not be necessary to set and clear these breakpoints.
