gnupic: 2 (sometimes/sometimes not) errors from gpsim


Previous by date: 31 May 2000 11:27:22 -0000 2 (sometimes/sometimes not) errors from gpsim, Martin Berentsen
Next by date: 31 May 2000 11:27:22 -0000 problem in 19.2, Matthew Bowles
Previous in thread: 31 May 2000 11:27:22 -0000 2 (sometimes/sometimes not) errors from gpsim, Martin Berentsen
Next in thread:

Subject: Re: 2 (sometimes/sometimes not) errors from gpsim
From: Scott Dattalo ####@####.####
Date: 31 May 2000 11:27:22 -0000
Message-Id: <Pine.LNX.4.21.0005310620300.29700-100000@tempest2.blackhat.net>


On Wed, 31 May 2000, Martin Berentsen wrote:

> Hi out there !
> 
> today I got these errors from gpsim (I've seen them sometimes
> in the last time, but I ignored them)
> 
> > Cycle_Counter::reassign_break - didn't find the old one
> > TMR0: bug TMR0 is larger than 255...       
> 
> What goes wrong ?
> The same PIC program runs yesterday without this message.

Matt saw this bug too. It was (supposedly) fixed in 0.19.1 . Are you still using
0.19.0 or did you download 0.19.2 and try that? If you're using 0.19.2, then
please send me your pic source code that causes gpsim to expose this bug.

BTW, the bug was caused by writing new values to TMR0. In a pic, there is a 2
cycle delay between writing a new value to TMR0 and having that new value take
affect. If during those two cycles another breakpoint disassociated with the
TMR0 peripheral occurred, there was a chance for the TMR0 count to get fouled
up.


Regards,
Scott


Previous by date: 31 May 2000 11:27:22 -0000 2 (sometimes/sometimes not) errors from gpsim, Martin Berentsen
Next by date: 31 May 2000 11:27:22 -0000 problem in 19.2, Matthew Bowles
Previous in thread: 31 May 2000 11:27:22 -0000 2 (sometimes/sometimes not) errors from gpsim, Martin Berentsen
Next in thread:


Powered by ezmlm-browse 0.20.