Yahoo Groups archive

Lpc2000

Index last updated: 2026-04-28 23:31 UTC

Message

Re: [lpc2000] Breakpoint not stopping timer

2005-11-15 by Michael Johnson

Hi Marko,

When a debugger backtraces off the end of the callstack it may 
unwittingly reference peripheral registers - could you be affected by 
this? We've stopped CrossStudio accessing peripheral registers when 
backtracing to handle this case.

Regards
Michael

>Hi,
>
>I am aware that reading periphery in some windows could clear some flags, but I don't have any "periphery window" opened....
>
>marko
>
>  
>
>>Od: "Dan Beadle" <dan.beadle@...>
>>Datum: 2005/11/15 Tor PM 04:06:02 CET
>>Za: <lpc2000@yahoogroups.com>
>>Zadeva: RE: [lpc2000] Breakpoint not stopping timer
>>
>>I have seen this when I have the VIC registers open in a window.  
>> 
>>As I recall, the issue is something like this:  When I hit the first
>>interrupt, another hit while stopped in the IRQ, then reading the VIC in
>>the debugger clears then pending timer int.  Then no more interrupts.
>>Generally, I keep the VIC register window closed.
>>
>>  _____  
>>
>>From: lpc2000@yahoogroups.com [mailto:lpc2000@yahoogroups.com] On Behalf
>>Of Marko Panger
>>Sent: Tuesday, November 15, 2005 6:26 AM
>>To: lpc2000@yahoogroups.com
>>Subject: [lpc2000] Breakpoint not stopping timer
>>
>>
>>Hi all,
>>
>>I am facing a  strange problem when debugging applications with match
>>compare timer interrupts enabled.
>>Hi all,
>>
>>I have a timer match IRQ which fires every 1ms. Basically a ticker.
>>Because the timer is used also for other purposes I add a value of
>>1000 to the timer match register to get the next interrupt after 1ms
>>(timer clock is 1Mhz). I do also increment a variable in the match IRQ.
>>
>>I have noticed that if I a put a breakpoint (it doesn't mater where,
>>IRQ or main loop) the IRQ isn't hit anymore. After playing around I
>>noticed that when the breakpoint is hit the timer still goes on for
>>some time, but without hitting the IRQ. Because of this the timer
>>count register goes ahead of the match register and the match does not
>>occur anymore. Further I discovered that when single stepping the
>>global ticker variable is incremented which means that single stepping
>>takes more than 1ms.
>>
>>I am wondering that the internal JTAG logic has some flavors or is
>>this my debugger issue ? Has anybody else noticed such a behavior ?
>>
>>Regards,
>>marko
>>
>>
>>
>>
>>
>>
>>SPONSORED LINKS 
>>Microprocessor
>><http://groups.yahoo.com/gads?t=ms&k=Microprocessor&w1=Microprocessor&w2
>>=Microcontrollers&w3=Pic+microcontrollers&w4=8051+microprocessor&c=4&s=9
>>3&.sig=tsVC-J9hJ5qyXg0WPR0l6g>  	Microcontrollers
>><http://groups.yahoo.com/gads?t=ms&k=Microcontrollers&w1=Microprocessor&
>>w2=Microcontrollers&w3=Pic+microcontrollers&w4=8051+microprocessor&c=4&s
>>=93&.sig=DvJVNqC_pqRTm8Xq01nxwg>  	Pic microcontrollers
>><http://groups.yahoo.com/gads?t=ms&k=Pic+microcontrollers&w1=Microproces
>>sor&w2=Microcontrollers&w3=Pic+microcontrollers&w4=8051+microprocessor&c
>>=4&s=93&.sig=TpkoX4KofDJ7c6LyBvUqVQ>  	
>>8051 microprocessor
>><http://groups.yahoo.com/gads?t=ms&k=8051+microprocessor&w1=Microprocess
>>or&w2=Microcontrollers&w3=Pic+microcontrollers&w4=8051+microprocessor&c=
>>4&s=93&.sig=1Ipf1Fjfbd_HVIlekkDP-A>  	
>>
>>  _____  
>>
>>YAHOO! GROUPS LINKS 
>>
>>
>>	
>>*	 Visit your group "lpc2000
>><http://groups.yahoo.com/group/lpc2000> " on the web.
>>	  
>>*	 To unsubscribe from this group, send an email to:
>>	 lpc2000-unsubscribe@yahoogroups.com
>><mailto:lpc2000-unsubscribe@yahoogroups.com?subject=Unsubscribe> 
>>	  
>>*	 Your use of Yahoo! Groups is subject to the Yahoo! Terms of
>>Service <http://docs.yahoo.com/info/terms/> . 
>>
>>
>>  _____  
>>
>>
>>
>>
>>[Non-text portions of this message have been removed]
>>
>>
>>
>>
>> 
>>Yahoo! Groups Links
>>
>>
>>
>> 
>>
>>
>>
>>    
>>
>
>
>
>
> 
>Yahoo! Groups Links
>
>
>
> 
>
>
>  
>

Attachments

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.