• State Not Answered
  • Locked Locked
  • Replies 33 replies
  • Subscribers 21 subscribers
  • Views 9895 views
  • Users 0 members are here
2025 survey

We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.

Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Setting all 8 breakpoints

Warden Reed

Hi everyone,

I am debugging an application on a STM32F4 in flash with a ULINK.
I read one of the features for the ULINK should be 8 breakpoints, but after the 6th breakpoint I get an error message.
Isn't it possible to use all 8 breakpoints?
Maybe can I use 8 breakpoints with another device?

Can you help me with this?

Warden

Parents
  • 0 Arm Employee Badge in reply to John Rodeo

    I did have it changed a long time ago: http://www.keil.com/ulink2/specs.asp

    Hello

    Last March this message timed out on me and I couldn't access it or even find it - I was waiting for someone to activate and now it looks like I have access ! Some sort of bug...
    So - I did get the webpage fixed in march or so: www.keil.com/.../specs.asp
    I asked them to change all other mention of the "8" - plus all my documents and I even told NXP about it as I saw they also used "8".
    The confusion results from the ability using the Watchpoint feature (aka Access Breaks) to set two additional breakpoints. The regular 6 hardware breakpoints can be set/unset while the program is running. The instruction at the breakpoint address is not executed when it is encountered. This is an important feature.
    The Watchpoint breakpoint, if I may call it this, must be set/unset when the program is stopped and it usually(always?) has some "skid". This is because these two types come from different parts of CoreSight. Someone, long ago, thought these are equal - and they are (sort of) , except for the skid.
    I tried this and it doesn't seem possible to set just a Watchpoint breakpoint on just an executable address in uVision (MDK 5.13)(MCB1700). Not sure why. I will ask the engineer about this. But, of course, I can set 6 hardware breakpoints the normal way. Try 7 and uVision complains as it should.
    If you know of anywhere else on keil.com that claims 8 - let me know. bob.boys@arm.com
    BTW - it really isn't ULINK or J-Link that determines the number of hardware breakpoints - it is the chip itself.
    Thanks
    Bob San Jose, California

Reply
  • 0 Arm Employee Badge in reply to John Rodeo

    I did have it changed a long time ago: http://www.keil.com/ulink2/specs.asp

    Hello

    Last March this message timed out on me and I couldn't access it or even find it - I was waiting for someone to activate and now it looks like I have access ! Some sort of bug...
    So - I did get the webpage fixed in march or so: www.keil.com/.../specs.asp
    I asked them to change all other mention of the "8" - plus all my documents and I even told NXP about it as I saw they also used "8".
    The confusion results from the ability using the Watchpoint feature (aka Access Breaks) to set two additional breakpoints. The regular 6 hardware breakpoints can be set/unset while the program is running. The instruction at the breakpoint address is not executed when it is encountered. This is an important feature.
    The Watchpoint breakpoint, if I may call it this, must be set/unset when the program is stopped and it usually(always?) has some "skid". This is because these two types come from different parts of CoreSight. Someone, long ago, thought these are equal - and they are (sort of) , except for the skid.
    I tried this and it doesn't seem possible to set just a Watchpoint breakpoint on just an executable address in uVision (MDK 5.13)(MCB1700). Not sure why. I will ask the engineer about this. But, of course, I can set 6 hardware breakpoints the normal way. Try 7 and uVision complains as it should.
    If you know of anywhere else on keil.com that claims 8 - let me know. bob.boys@arm.com
    BTW - it really isn't ULINK or J-Link that determines the number of hardware breakpoints - it is the chip itself.
    Thanks
    Bob San Jose, California

Children
No data