Breakpoints problem

Comments

13 comments

  • Avatar
    Dr Danish Ali

    Have you seen https://rowley.zendesk.com/entries/48410795-Breakpoints-Stop-Working ?

    It might be the same problem you're reporting, and there is a "nightly build" which seems to solve it for me.

     

    Hope this helps,

    Danish

    0
    Comment actions Permalink
  • Avatar
    Paul Bayton

    Thanks. I will try 3.6.2

    Actually Its been a problem for a little while now - since 3.5 I think. Just getting fed up and like to see it solved.

    0
    Comment actions Permalink
  • Avatar
    Michael Johnson

    Is the application executing an __asm("wfi") instruction?

    0
    Comment actions Permalink
  • Avatar
    Paul Bayton

    No, just standard code.

    0
    Comment actions Permalink
  • Avatar
    Michael Johnson

    Does it make a difference if you set "Use Builtin Flash Loader" to "No" on the j-link target properties.

    0
    Comment actions Permalink
  • Avatar
    Paul Bayton

    It still fails using the normal flash loader

    0
    Comment actions Permalink
  • Avatar
    Michael Johnson

    If you disconnect after each debug session does this change things?

    0
    Comment actions Permalink
  • Avatar
    Paul Bayton

    Not Really

    Looking at the jlink log file, the problem seems to be when a breakpoint is removed.

    normally when one is added the following command is sent: e.g.

    T35F8 2191:143 JLINK_WriteU32(0xE0002008, 0x8801DB5B) - FP_COMP[0]

    But that does not happen again once a breakpoint is removed.

    PS I cant find any reference to this address in the manuals.

    0
    Comment actions Permalink
  • Avatar
    Paul Bayton

    Hi

    Yes, I can confirm its the FlashPatch comparitor registers that are not being set after a breakpoint is removed.

    0
    Comment actions Permalink
  • Avatar
    Michael Johnson

    I'd expect to see

    JLINK_WriteU32(0xE0002008, 0x8801DB5A)

    when the breakpoint is deleted i.e. the bottom bit is cleared.

    0
    Comment actions Permalink
  • Avatar
    Paul Bayton

    Yes, bit0 is cleared when removing or disabling, but no WriteU32 operations occur when setting them afterwards during program run.

    0
    Comment actions Permalink
  • Avatar
    Michael Johnson

    So the breakpoint is not cleared at the end of a debug session?

    0
    Comment actions Permalink
  • Avatar
    Paul Bayton

    Yes, they are cleared when stopping

    Its when breakpoints are added/removed during a debug session (in run mode) that there is a problem.

    After any breakpoint is removed, no more can be added.

    0
    Comment actions Permalink

Please sign in to leave a comment.