[<<] [<] Page 1 of 1 [>] [>>] | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Subject:
Re. gpsim, an error in the names?
From: ####@####.#### Date: 23 Jan 2004 18:05:31 -0000 Message-Id: NĂ©stor A. Marchesini wrote:- .... > ReadEeprom > bcf STATUS,RP0 > bsf STATUS,RP1 > movwf EEADR > bsf STATUS,RP0 > bcf EECON1,EEPGD > bsf EECON1,RD > bcf STATUS,RP0 > movf EEDATA,W > bcf STATUS,RP1 > return > > gpsim> step > 0x0000000000000012 p16F873 0x0058 0x2068 call 0x0068 > SetPC address = 0x68, row = 265 > gpsim> step > 0x0000000000000014 p16F873 0x0068 0x1283 bcf status,5 > read: 0x3c from status > wrote: 0x1c to status > SetPC address = 0x69, row = 266 > gpsim> step > 0x0000000000000015 p16F873 0x0069 0x1703 bsf status,6 > read: 0x1c from status > wrote: 0x5c to status > SetPC address = 0x6a, row = 267 > gpsim> step > 0x0000000000000016 p16F873 0x006A 0x008D movwf pir2v2 > read: 0x00 from W > wrote: 0x00 to eeadr > SetPC address = 0x6b, row = 268 > Is this what gpsim's output looks like ? Looks interesting. Many of us become wary of downloading projects which will just consume time without helping to progress. I had an impression that gpsim was M$-Win-based ? == Chris Glur. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Subject:
Re: Re. gpsim, an error in the names?
From: David Willmore ####@####.#### Date: 23 Jan 2004 22:25:32 -0000 Message-Id: <200401232202.i0NM2iqe002751@localhost.localdomain> > Is this what gpsim's output looks like ? Looks interesting. > Many of us become wary of downloading projects which will just > consume time without helping to progress. > > I had an impression that gpsim was M$-Win-based ? That is the output of the text window from which gpsim is launched. It has a nice textual debugger interface just like gdb and friends. So, if that's all you want, you can use just that. At this stage of development, it's important to have that kind of low level access to debug gpsim itself. For me, that window is covered up by the graphical windows that display the code, the registers, the watch window, the virtual breadboard, etc. Only if something goes wrong, do I need to look at that window. So, you're right, it is a nice graphical application. I was actually quite stunned the first time I ran it. It has a lot of wonderful features that I have come to love. Gpsim has certainly helped my coding! It may not be perfect, but it's better than my code tends to be. :) Cheers, David | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Subject:
Re: Re. gpsim, an error in the names?
From: Scott Dattalo ####@####.#### Date: 24 Jan 2004 01:58:34 -0000 Message-Id: <Pine.LNX.4.44.0401231719560.14740-100000@ruckus.brouhaha.com> On -1 xxx -1 ####@####.#### wrote: <snip> > I had an impression that gpsim was M$-Win-based ? Interesting. Based on your recent GNUPIC mailing list activity, I had the impression you knew what gpsim was. Read all about gpsim here: http://www.dattalo.com/gnupic/gpsim.html Scott | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
[<<] [<] Page 1 of 1 [>] [>>] |