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.

TMS320F280039: CCS 20.2 - How to set an hardware breakpoint to program memory?

Part Number: TMS320F280039

Tool/software:

I'm trying the latest CCS 20.2, and I still find it pretty hard to use in debugging, compared to v.12.8.1

With CCS 12.8.1, I can set a hardware breakpoint in program memory simply by right-clicking on the line and selecting "Breakpoint (Code Composer Studio) > Hardware breakpoint" from the contextual menu.

With CCS 20.2, on the same target, the only option is a software breakpoint. As an alternative, there is a "Hardware watchpoint", for which I have to specify the memory address, which is quite impractical.

Are hardware breakpoints supported at all?

  • Hi Luca,

    For the hardware watchpoint, you should also be able to specify the line number for where you want this hardware watchpoint to occur. 

    Regards,

    Peter

  • Peter,

    1. The setup is cumbersome compared to the older one
    2. It can only be achieved from the Breakpoints panel "... More Actions" (which is not quite obvious)
    3. Finally, it doesn't work here - see the example below, where a software breakpoint (F9) works, and the hardware watchpoint isn't resolved - after all, this is an HW watchpoint on Data Memory, and I still can't find any HW breakpoint anywhere else in the UI

  • Hi Luca,

    I believe the location path also includes references to the workspace that the project is in. You can check the specific location by setting a software breakpoint and looking at the properties of the breakpoint for the location field.

    Hardware Watchpoint is a different concept than HW breakpoint and HW breakpoint afaik is not currently supported in the latest version of the tool though it should be in the pipeline to port over from 12.8. If you absolutely need to use HW breakpoint over SW breakpoint, then it is necessary to use the older version of CCS until that feature is pulled into CCS v20

    Regards,

    Peter