• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 31 subscribers
  • Views 214 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.

TMS570LS3137-EP: Breakpoint issue

Subash Sundaresan1
Intellectual 560 points

Part Number: TMS570LS3137-EP
Other Parts Discussed in Thread: TMS570LS3137

We are using TMS570ls3137 in our project and development tool is Code Composer Studio Version: 10.2.0.00009,  compiler version is TI v20.2.4 LTS. We are facing inconsistency in setting breakpoint.  We observed few scenarios:

Scenario-1:

When there is local variable or function parameter we are able to set breakpoint at function start scope ( at open brace "{" ) as expected .

Scenario-2:

When there is no local variable or no function parameter we are unable to set breakpoint at function start scope ( at open brace "{" ) as expected . If we forcefully set break point, CCS showing annotation that there is no executable on the particular line.

As are doing automated testing we wanted to keep the breakpoint consistently at function start scope which is open brace "{".

In the second function, our expectation to set breakpoint at line number 189, but it automatically sets at 190. is there any workaround to address this issue?

 

  • 0
    TI__Guru 72500 points

    Breakpoints need to exist on a single assembly instruction. Depending on what the compiler and optimizer does, not every line in a C program generates assembly instructions. However, it you want to add a breakpoint on the first instruction of a function, use the function name instead of the line number. From the pulldown menu select "Run" -> "New Breakpoint" -> "Hardware Breakpoint" , then the name of the function such as "testWithOutParam".