Part Number: DK-TM4C129X
Tool/software: Code Composer Studio
It seems that CCS can get in a state where it loses track of the number of AET resources available. I have been monitoring expressions in real time while the target is running, and occasionally setting breakpoints with no trouble. But now, attempts to set any breakpoint cause the "Error enabling this function: There is no AET resource to support this job." popup. I have the following debug option settings:
and
.
I am not monitoring any expressions when I attempt to set the breakpoint. For a while, disabling CIO function use would enable at least one breakpoint to be set, but, now, that doesn't even help. And, anyway, I need the CIO functions to enable System_printf(). I think that CCS sometimes just forgets AET resources and renders itself unable to set breakpoints.
