• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 52 subscribers
  • Views 6882 views
  • Users 0 members are here
Support feedback
Options
Options

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.

Problem setting CCS breakpoints?

Gordon Deane
Expert 1255 points
Other Parts Discussed in Thread: TMS320C6678

Hi,

I recently upgraded my desktop machine from CCS 5.1.0.09000_win32 to 5.2.1.00018_win32.  Now I find that when I'm debugging and double-click to set a breakpoint, it doesn't work. 

It seems CCS is setting a "C/C++ breakpoint" rather than a "Code Composer Studio Breakpoint".  (See capture below.  The breakpoint icon lacks a checkmark, and on a CCS 5.1 machine I get "Code Composer Studio Breakpoint" as the default option on the submenu below.

I can get working breakpoints by then going into the breakpoint type and forcing a hardware breakpoint, which is a bit annoying.  I had some difficulties in the upgrade process so fear there is a configuration problem here.  I ended up deleting c:\ti\ccsv5 and reinstalling, but didn't want to get rid of c:\ti entirely. 

The target is a custom TMS320C6678 board closely based on the EVM, and the emulator is a recent BlackHawk XDS560v2 USB.   The exact same board, emulator and GEL file work fine under CCS 5.1.

UPDATE: If I right-click in the editor and select "Breakpoints (Code Composer Studio) > Breakpoint" I get a proper software breakpoint.  It's just the double-click action in the editor that creates broken ones.

  • 0
    TI__Guru**** 173310 points

    Gordon,

    Could you first double-check that you are indeed in the "CCS Debug" perspective? I found this thread on a similar issue, could you please take a look and see if the suggestions help?

    The other thing I would suggest is to try cleaning the workspace or trying with a new workspace to see if that helps revert it back to the proper type of breakpoint:
    http://processors.wiki.ti.com/index.php/Troubleshooting_CCSv5#General_IDE

  • 0 in reply to AartiG
    Expert 1255 points

    Thanks for the link, this one solved it:

    "Open the .project file in your project and add 'com.ti.ccstudio.debug.ccsBreakpointNature' to the nature section at the end of the file. You might need to close the project and open it again."

    I am using a Makefile project because I was tearing my hair out trying to get the CCS project to do what I want, particularly with respect to checking out cleanly in SVN and Just Working.  Also I couldn't work out how to have a non-Makefile project automatically remade when a Makefile library project it depends on changes.  Upgrading to CCS 5.2 and finding that half my projects randomly broke was the final straw.  Finding that you have to know in advance whether a project is Makefile based or not to use different Import mechanisms was the other.  My makefile works quite nicely for command line development, I'm mostly using CCS for debugging.

    Another wishlist item while I'm here:  it would be very handy if external Makefile projects could benefit from at least some of the CCS project nature.  For example, being able to have a per-project RTSC project config which (a) fed the debugger ROV setup (rather than using a workspace-global RTSC config) and (b) set the XDCPATH for the Makefile automatically. That would be great.

    Regards,

    Gordon