gnupic: Re: [gnupic] gpsim weirdness
Subject:
Re: [gnupic] gpsim weirdness
From:
"Scott Dattalo" ####@####.####
Date:
29 Dec 2005 02:13:30 +0000
Message-Id: <63694.71.139.4.16.1135815668.squirrel@71.139.4.16>
> On Wed, 2005-12-28 at 23:25, John De Villiers wrote:
>> Im having a terrible time getting a program to simulate correctly.
> And here comes the file - at last
Hi John,
I tried your modified LCD driver with the latest version of gpsim and the
LCD module. I can also confirm that this code is failing. It's not obvious
to me if the problem is with gpsim (and the LCD module) or with your code.
What I can say is that the unmodified version of the LCD driver (the one
that is part of gpsim's LCD examples) works correctly. It appears that
your version fails during the LCD initialization at the point where ASCII
spaces are written to the display. For some reason the LCD ready bit is
not getting asserted while the 4'th ASCII space is being written.
BTW, I did find a new gpsim segv while debugging your code. A recent
change to the break point code makes the assumption that all ram data has
an associated symbol table entry. However, gpasm's local symbols do not
get put into gpsim's symbol table. Consequently those registers *do not*
have symbols. If you attempt to set a break on one of these gpsim would
crash. Any way, I fixed this and will check it into CVS shortly.
Scott
