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.

Unable to make Stellaris ICDI debugger work for Tiva C from CC6 in Ubuntu

Other Parts Discussed in Thread: EK-TM4C123GXL

I'm trying to make the Stellaris In-Circuit Debug Interface work on a Tiva C TM4C1294 Connected LaunchPad from Code Composer Studio 6.0.1 in Ubuntu 12.04 where the used compiler is GNU v4.7.4 (Linaro).

I have made a simple CCS Project and chosen to "Reset target during program load to Flash memory" under the Project Properties -> Debug -> Flash Settings.

The problem is that I'm unable to make it stop at a breakpoint.

The exact same scenario have I tried from windows, where it successfully stops at the desired breakpoint.

Do you have an idea what might cause the problem?

Thanks, Jesper

  • Jesper Hansen said:

    The problem is that I'm unable to make it stop at a breakpoint.

     In your writing I infer you have a running version so you launched driver installation script and they work. Are you able to do single step or also this refuse to work?

     I am not using GCC but TI compiler and all work fine. Please can you post more information on error when you launch your code?

     Ubuntu is 32 or 64 bit version?

     Installation script?

     Errors appear on console when you set breakpoint.

  • My mistake. I have been a little confused about software / hardware breakpoints.
    If I set the breakpoints before the debugger is run, it will automatically make a software breakpoint, which is the reason why it didn't halt. If instead I change the breakpoint to hardware breakpoint while it is debugging, it will succesfully halt at the right spot.

    Do you know if it is possible to set H/W breakpoints without running the debugger?

    Thanks, Jesper
  • Jesper Hansen said:
    Do you know if it is possible to set H/W breakpoints without running the debugger?

     I don't understand what did you intend with this, breakpoint are a feature of debugger so what do you intend assign to that point? Breakpoint in hardware come from a special unit embedded on chip, if software a special instruction is substituted to code that is saved by debugger, on runtime this is an ISR service on your code.

    Please ask again if not by wording  also with some example.

     Please also correct title from utuntu to Ubuntu to improve search and readability.

  • Jesper Hansen said:
    If I set the breakpoints before the debugger is run, it will automatically make a software breakpoint, which is the reason why it didn't halt. If instead I change the breakpoint to hardware breakpoint while it is debugging, it will succesfully halt at the right spot.

    Using CCS 6 running under Linux with a EK-TM4C123GXL I haven't been able to repeat the failure. The sequence was:

    1) Set a breakpoint when no active debugging session. The Breakpoints Window reports that apparently that a S/W break point has been set.

    2) Start a debugging session. The Breakpoints Window now reports that the breakpoint is now a H/W breakpoint.

    3) Resume the program, and the breakpoint is hit.

    There are the following threads which explain that CCS automatically uses H/W breakpoint on ARM targets:

    - Setting software breakpoints on TMS570LS0432 in CCS6

    Minor bug in breakpoints view on CCS6.0.0.00040 (TMS570LS0432)

    On the Linux system where the breakpoint fails to be hit, under CCS Project Properties -> Debug -> Auto Run and Launch Options -> Launch Options is "Restore breakpoints from previous session" enabled?

  • Yes, "Restore breakpoints from previous session" is enabled.

    Here is what happens:

    I disable "Allow software breakpoints to be used" in "Debug -> Misc/Other Options" and set two breakpoints before running the debug session:

    Then when I start the debug session, the two S/W breakpoints will be turned into H/W breakpoints, but they are now disabled.

    I guess it's just some option that I have not correctly set.

    Do you have any ideas?

    Thanks, Jesper

  • Jesper Hansen said:
    Do you have any ideas?

    I still can't repeat the problem.

    When you hover the mouse over the breakpoints with the "exclamation marks" symbol on them, is there any explanatory text displayed about why the breakpoints are disabled?

    If you right-click on the disabled breakpoints, and display the breakpoint properties, what is displayed?