> On 16 Jul 2023, at 22:13, Tomas Vanek <tom_...@users.sourceforge.net> wrote: > > Just to be sure, check the counter with J-Link and ST-LINK GDB server I placed a breakpoint on the `pendsv_cnt++;` in the PendSV_Handler, and an Expression watch in Eclipse on the `pendsv_cnt` variable. With both the J-Link and the ST-LINK GDB server, the PendSV_Handler was invoked only once (the breakpoint was hit once, and the watch reads the value of 1), although this should not happen if the interrupts are disabled at reset. The difference is that with the J-Link, the rogue breakpoint is not hit even once. So... you were right. :-) Sorry for overlooking this in my previous test. Liviu
- Re: semihosting unexpected bre... Tommy Murphy
- Re: semihosting unexpected bre... Liviu Ionescu
- Re: semihosting unexpected bre... Liviu Ionescu
- Re: semihosting unexpected bre... Tommy Murphy
- Re: semihosting unexpected bre... Tomas Vanek
- Re: semihosting unexpected bre... Liviu Ionescu
- Re: semihosting unexpected bre... Liviu Ionescu
- Re: semihosting unexpected bre... Tomas Vanek
- Re: semihosting unexpected bre... Liviu Ionescu
- Re: semihosting unexpected bre... Tomas Vanek
- Re: semihosting unexpected bre... Liviu Ionescu
- Re: semihosting unexpected bre... Tomas Vanek
- Re: semihosting unexpected bre... Liviu Ionescu
- Re: semihosting unexpected bre... Tommy Murphy
- Re: semihosting unexpected bre... Liviu Ionescu
- Re: semihosting unexpected bre... Tommy Murphy
- Re: semihosting unexpected bre... Liviu Ionescu
- Re: semihosting unexpected bre... Tomas Vanek
- Re: semihosting unexpected bre... Michael Schwingen
- Re: semihosting unexpected bre... Liviu Ionescu
- Re: semihosting unexpected breakpoint not acknowledged James Murray