• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 55 subscribers
  • Views 476 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.

CCS/CC1352P: Breakpoints not working with JLink

Yvan Pearson
Intellectual 850 points
Part Number: CC1352P
Other Parts Discussed in Thread: SEGGER

Tool/software: Code Composer Studio

I can't seem to get breakpoints to work with the Segger JLink (on my custom board) but breakpoints seem to work OK with the XDS110 (Using the launchpad board).

Any ideas?

  • 0
    TI__Guru**** 162895 points

    Yvan,

    This is what I see.  I am running CCSv9.3.0 and I have a CC1312R1 LaunchPad.

    I setup the pwmled2 example.

    Debug with the onboard XDS110.

    Setup a couple of breakpoints.

    Breakpoints are working.

    I then remove all of the jumpers between the XDS110 section of the LaunchPad and the target board section with the exception of the GND, 5V and 3V3.  I then connect my JLink to the 10pin header on the target section of the board.  Next I change the ccxml file in my project to use Jlink.

    Launch debug.  Halts at main fine (we set a breakpoint there).

    I try running and it skips over the breakpoints that I had set before.  I click restart to go back to main().  I try stepping and that works fine (which uses breakpoints)

    I then clear the breakpoints that were set before and set new ones.  Now when I run it halts fine at the breakpoints.

    I noticed that the breakpoints I set when using the XDS110 had the h/w breakpoint icon (has the cross hairs on them) but when I set them after configuring for JLink I see the plain round icon which typically indicates a software breakpoint.  Breakpoint handling when using the JLink is a bit funny as CCS usually wants to manage the breakpoints but the Segger stack also wants to do that.  Thus in my case I think CCS was telling the Segger stack to set a h/w breakpoint which it may be rejecting as it just wants CCS to tell it to do breakpoint and then the Segger stack figures out what type to set.

    Can you try clearing breakpoints and setting them again to see if that works.  Does it halt at main() ok?  Does stepping work?

    Regards,

    John