gnupic: Re: Gpasm comments
Subject:
FW: Gpasm comments
From:
Simon Wood ####@####.####
Date:
18 Dec 2000 15:52:20 -0000
Message-Id: <44632C76B97BD211AF6B00805FADCAB202D7392A@exchange.saltaire.pace.co.uk>
It appears that James is no longer with SGI, so perhaps someone on this list can help with my comments/questions.
Simon Wood
> -----Original Message-----
> From: Simon Wood
> Sent: Monday, December 18, 2000 3:43 PM
> To: ####@####.####
> Subject: Gpasm comments
>
> Hi James,
> I've just started looking at PIC's and was glad to see that there are some Linux tools available. I downloaded the CVS version and am attempting to compile some code (to make a chorded keyboard - pickey.asm).
>
> Comments and questions:
> 1). The CVS download instructions on sourceforge neglect to tell you the module name (or is it an intelligence test??), I ended up using '.' which dumped everything in the local directory rather than creating a new one.
>
> 2). The code I'm using makes heavy use of macros, but your parser was falling over with 'Expression too complex'. After a bit of digging around I worked out it is because the parser is not case sensitive and it was getting confused by 'VALUE' and 'value' and seeing them as the same entity:
> #define VALUE 0x11
>
> fred macro value
> MOVLW value
> endm
>
> Is there an easy way to change this??
>
> 3). Again with macros, in the following the use of variable 'end' seems to confuse the parser.... doesn't really need to be fixed though, I'll just work around it with 'mend' or something.
> ensure_table: macro start, end
> if ((high start) - (high end)) !=0
> ERROR start
> endif
> endm
>
> 4). The code appears to use a 'standard' include file (P16C63.INC) for the common name/port specifications. I've had a look around on the web but couldn't find them. Do you have any pointers?
>
> Thanks in advance,
> Simon Wood
>
