• State Resolved
  • Locked Locked
  • Replies 9 replies
  • Answers 1 answer
  • Subscribers 53 subscribers
  • Views 10890 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

Breakpoint Manager: There is no AET resource to support this job

Keyur Hariya
Prodigy 80 points
Other Parts Discussed in Thread: CC2650

1. OS- Windows 10 Home
2. CCS- Version 6.0.0.00190
3. Board- EK-TM4C123GXL | Emulator- Stellaris In Circuit Debug Interface

Hello, I'm building a RTOS on this board and when I'm trying to put breakpoints in my code, it gives the following error "Error enabling this function: There is no AET to support this job." I tried disconnecting the board and setting breakpoints, I can put many of them but when it's connected I can set only 4 breakpoints at max. I have also tried to put break point in some simple code it allows me to put a few more than 4 and then this error pops up !

Please help me.

  • 0
    TI__Guru**** 463561 points
    Hello,
    When trying to set breakpoints for code in flash, a "hardware" breakpoint is used. There is only a limited amount of these.
    processors.wiki.ti.com/.../Stellaris_support_in_CCS

    I think for Tiva C, there are 6 breakpoints available and it is likely you only can set 4 because the others are used automatically by the debugger (exit point, run to main, C I/O, etc). You can try disabling some of these options and see if this helps:
    e2e.ti.com/.../1766863

    Thanks
    ki
  • 0 in reply to Ki
    Guru 16361 points

    Ki-Soo Lee said:

    I think for Tiva C, there are 6 breakpoints available and it is likely you only can set 4 because the others are used automatically by the debugger (exit point, run to main, C I/O, etc). You can try disabling some of these options and see if this helps:
    e2e.ti.com/.../1766863

    I'm using CC2650 rather than Tiva, but I think I've seen CCS* use up multiple AET resources for a single breakpoint placed in source code. I get the same warning as Keyur, but the breakpoint list shows only one entry. When it happens I've been able to work around it by removing the breakpoint from the source code and placing it in the disassembly view instead.

    EDIT: I'm don't know if this is a known issue; if not I can try to repro and will post another thread with more details.

    * I'm using CCS6.1.1.00022

  • 0 in reply to Robert Cowsill
    TI__Guru**** 463561 points
    Depending on the type of breakpoint, more AET resources may be used. For example, a HW breakpoint that halts the target when reached should use just one resource. But if the breakpoint has a different action or trigger (like halt on specific condition (besides when address reached) or do not halt when reached but do action "X"), more resources can be used.

    Thanks
    ki
  • 0 in reply to Ki
    Prodigy 80 points

    Hi Ki, thanks for your reply, I got to learn about breakpoints better. but I tried to disable them, but could find a option as mentioned in your link.
    Can you please tell me where I can find them for the configuration I mentioned in my post? Or can I replace them with software breakpoints, if possible?

    I also tried to work around by adding breakpoints to disassembly instead of source code but didn't help me, as mentioned by Robert.

  • 0 in reply to Ki
    Guru 16361 points

    Ki-Soo Lee said:
    Depending on the type of breakpoint, more AET resources may be used. For example, a HW breakpoint that halts the target when reached should use just one resource. But if the breakpoint has a different action or trigger (like halt on specific condition (besides when address reached) or do not halt when reached but do action "X"), more resources can be used.

    Thanks, Ki. The breakpoints I'm having trouble with are just ordinary HW breakpoints, no special conditions or actions. I'll try to get a reliable repro setup for it.

  • 0 in reply to Keyur Hariya
    TI__Guru**** 463561 points

    Keyur Hariya said:
    ut I tried to disable them, but could find a option as mentioned in your link.
    Can you please tell me where I can find them for the configuration I mentioned in my post?

    See the below post:

    https://e2e.ti.com/support/development_tools/code_composer_studio/f/81/p/489225/1766863#1766863

    Keyur Hariya said:
    Or can I replace them with software breakpoints, if possible?

    If the code is in flash, then a hardware breakpoint must be used.

    Thanks

    ki

  • 0 in reply to Ki
    TI__Guru**** 463561 points

    Ki-Soo Lee said:

    See the below post:

    https://e2e.ti.com/support/development_tools/code_composer_studio/f/81/p/489225/1766863#1766863

    Forgot to mention that you can access the options via "Tools->Debugger Options'. The ones of interest are the load options and the run/launch options (first two under that menu)

  • 0 in reply to Ki
    Guru 16361 points

    Ki-Soo Lee said:
    Keyur Hariya
    Or can I replace them with software breakpoints, if possible?

    If the code is in flash, then a hardware breakpoint must be used.

    ...unless you want to embed the software breakpoints in your code at build time, which means they're always present and can't be disabled at debug time. Sometimes that's useful, for example in the fault trap and default ISRs you can break into the debugger rather than just looping forever.

  • 0 in reply to Robert Cowsill
    Prodigy 80 points
    Thanks Ki, disabling those options gave me 1 more breakpoint.