gnupic: Thread: Re: [gnupic] gpsimWin32

----- Original Message ----- 
From: "Tamas Rudnai" ####@####.####
To: ####@####.####
Sent: Wednesday, May 02, 2007 8:16 AM
Subject: [gnupic] gpsimWin32


> Hi Lads,
>
> I've just tried out gpsimWin32 on my XP box, and when I'd like to load and
> see the source code it just does not display it in the window. If I try to
> see the source code using list command, it says:
> ...
> Warning, you need to upgrade to gputils-0.13.0 or higher
> (Your assembler version is  MPASM)
> p10F202 is not a valid processor.
> (try 'processor list' to see a list of valid processors.
You paid too much attention to the wrong errors.  The ones above are 
important.

gpsim has trouble with output files produced by MPASM (except maybe much 
older versions of MPASM).  You will notice that if you type 'proc list', 
pic10f202 is listed, but it's saying p10F202 is not a valid processor.  One 
of the differences with the newer MPASM is the upper/lower-case of the proc 
name.  gpsim supports "pic10f202", "PIC10F202", "p10f202", and "P10F202" 
(IIRC), but *not* "p10F202" (notice the mixed case).

Install gputils for windows and gputils-mplab from 
www.sourceforge.net/projects/gputils.  Then select gputils as the MPLAB 
language toolsuite and reassemble your project.  That should solve your 
problems.

> ...
> 2. What does it mean HLL? I've written my code fully in Assembly
That isn't an error, just a message that prints for everyone.  It tells you 
gpsim doesn't know about high level language files for debugging, so it 
wouldn't trace through your original C source code if you did the project in 
C.

David 

Hi David,

Thanks very much for the info. This case sensitive comparison is so annoying
then. It is very easy to fix such a bug in gpsim. Is that a known issue so
that will be fixed the next release or will be left as it is?

Anyway, I've done what you said and it works perfectly so at the moment I'm
happy and exploring gpsim features.

Thanks again,
Tamas




On 5/2/07, David Barnett ####@####.#### wrote:
>
> ----- Original Message -----
> From: "Tamas Rudnai" ####@####.####
> To: ####@####.####
> Sent: Wednesday, May 02, 2007 8:16 AM
> Subject: [gnupic] gpsimWin32
>
>
> > Hi Lads,
> >
> > I've just tried out gpsimWin32 on my XP box, and when I'd like to load
> and
> > see the source code it just does not display it in the window. If I try
> to
> > see the source code using list command, it says:
> > ...
> > Warning, you need to upgrade to gputils-0.13.0 or higher
> > (Your assembler version is  MPASM)
> > p10F202 is not a valid processor.
> > (try 'processor list' to see a list of valid processors.
> You paid too much attention to the wrong errors.  The ones above are
> important.
>
> gpsim has trouble with output files produced by MPASM (except maybe much
> older versions of MPASM).  You will notice that if you type 'proc list',
> pic10f202 is listed, but it's saying p10F202 is not a valid
> processor.  One
> of the differences with the newer MPASM is the upper/lower-case of the
> proc
> name.  gpsim supports "pic10f202", "PIC10F202", "p10f202", and "P10F202"
> (IIRC), but *not* "p10F202" (notice the mixed case).
>
> Install gputils for windows and gputils-mplab from
> www.sourceforge.net/projects/gputils.  Then select gputils as the MPLAB
> language toolsuite and reassemble your project.  That should solve your
> problems.
>
> > ...
> > 2. What does it mean HLL? I've written my code fully in Assembly
> That isn't an error, just a message that prints for everyone.  It tells
> you
> gpsim doesn't know about high level language files for debugging, so it
> wouldn't trace through your original C source code if you did the project
> in
> C.
>
> David
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ####@####.####
> For additional commands, e-mail: ####@####.####
>
>

----- Original Message ----- 
From: "Tamas Rudnai" ####@####.####
To: ####@####.####
Sent: Wednesday, May 02, 2007 2:14 PM
Subject: Re: [gnupic] gpsimWin32


> Hi David,
>
> Thanks very much for the info. This case sensitive comparison is so 
> annoying
> then. It is very easy to fix such a bug in gpsim. Is that a known issue so
> that will be fixed the next release or will be left as it is?
I don't know the details, but I've always gotten the impression there were 
more issues with MPASM output files than just the letter case.  I wouldn't 
call it a bug per se, but I would like to see gpsim support MPASM output 
files eventually.  I haven't seen much discussion about it yet.

Just count yourself fortunate that your project assembles with gputils; 
there are still a few assembler features (like #v syntax) that work 
differently or don't work at all in gputils.  Until either those or MPASM 
output files are fixed, some of the more exotic projects (just a few) can't 
be debugged with gpsim at all.

BTW, it's perfectly fine to discuss gpsim on this list, but there is also a 
list specific to gpsim at ####@####.#### where gpsim 
features and development are discussed.

David 

On Wed, 2007-05-02 at 08:53 -0500, David Barnett wrote:

> gpsim has trouble with output files produced by MPASM (except maybe much
> older versions of MPASM).  You will notice that if you type 'proc list',
> pic10f202 is listed, but it's saying p10F202 is not a valid processor.
> One
> of the differences with the newer MPASM is the upper/lower-case of the
> proc
> name.  gpsim supports "pic10f202", "PIC10F202", "p10f202", and "P10F202"
> (IIRC), but *not* "p10F202" (notice the mixed case).

Since I don't use MPASM, I was unaware of this issue. In my opinion, gpsim
should support MPASM generate files...

BTW, I have also added support for the 10f204 and 10f206, but have not
checked this code in yet.

Scott

Thanks Scott,

I found gpsim very useful, it seems it's quite fast and as I can see it goes
inside macros as well which is important for me as I use macros extensively.
In addition as far as I can see you can use some external devices like LCD
modules.

Well done!

Tamas



On 5/2/07, Scott Dattalo ####@####.#### wrote:
>
> On Wed, 2007-05-02 at 08:53 -0500, David Barnett wrote:
>
> > gpsim has trouble with output files produced by MPASM (except maybe much
> > older versions of MPASM).  You will notice that if you type 'proc list',
> > pic10f202 is listed, but it's saying p10F202 is not a valid processor.
> > One
> > of the differences with the newer MPASM is the upper/lower-case of the
> > proc
> > name.  gpsim supports "pic10f202", "PIC10F202", "p10f202", and "P10F202"
> > (IIRC), but *not* "p10F202" (notice the mixed case).
>
> Since I don't use MPASM, I was unaware of this issue. In my opinion, gpsim
> should support MPASM generate files...
>
> BTW, I have also added support for the 10f204 and 10f206, but have not
> checked this code in yet.
>
> Scott
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ####@####.####
> For additional commands, e-mail: ####@####.####
>
>