Post by thread:Alternative PIC assembler

I wasn't to happy with the standard PIC assembler, so I have written an alternative version. Its primarily for 16C84 use. I have used it for a couple of programs and it seems to work okay. I don't know if anyone is interested in this. I can compile to 286 based DOS and uuencode, but its a bit long to post to the pic list. I could set up a mail responder to automatically email copies to people I suppose. Anyone who thinks its a good idea, send me an email. The main features are :- Block structure - you can use BEGIN and END labels in the code and nest them. You can then use LOOP or EXIT to goto the corresponding BEGIN or END. e.g. BEGIN BTFSC STATUS,Z EXIT ; Generates a GOTO to the coresponding END ... ; other code here... END Bit addresses - you can define variables that are bit addresses and use them directly in bit operations. e.g. instead of defining C as 0, it is defined as STATUS#0 and can be used as BSF C, or BTFSC C rather than BSF STATUS,C or BTFSC STATUS,C - you can defined a whole set of bit addresses in one go, e.g. STATUS#C#DC#Z#PD#TO#RP0#RP1#IRP = 3 ; define status register and its bits Alternative op codes - as well as the standard op codes, some simpler versions are supported. e.g. ANDW f rather than ANDWF f,W, and ANDF f rather than ANDWF f,F and ANDW #5 rather than ANDLW 5. Op codes for bit addresses are simpler also - The standard op codes are supported as well and can be mixed in with new ones. - There are also IF / IFN op codes for bit test and skip e.g. IF C GOTO TEST will generate BTFSC STATUS,C followed by GOTO TEST Allocation - you can use RAM and BIT pseudo variables as being the "next byte of RAM" e.g. instead of :- use :- FLAG = 0D FLAG = RAM DATA = 0E DATA = RAM CTRL1= 0F CTRL1= RAM - you can allocate bits in the same way Comments ? -- _ (_) _| _ . _ _ Tel +44 973 222257 ( )(_|( |(_|| ) Fax UK 0500 222258 E&OE

-----BEGIN PGP SIGNED MESSAGE----- On Sat, 4 Nov 1995, Adrian Kennard wrote: >I wasn't to happy with the standard PIC assembler, so I have written an >alternative version. Its primarily for 16C84 use. I have used it for a >couple of programs and it seems to work okay. > >I don't know if anyone is interested in this. I can compile to 286 based DOS >and uuencode, but its a bit long to post to the pic list. I could set up a >mail responder to automatically email copies to people I suppose. I'm interested... especially if you're going to release the source-code! Hopefully, you've written it in ANSI C so I can compile it under Linux!! (PIC16C84 program-download code is already out there, somewhere...) Boy, I'd *love* it if I wouldn't have to keep DOS around for PIC development. Rick Miller, Design Engineer (and local "Internet Guy") Digalog Systems, Inc. <.....rickKILLspam@spam@digalogsys.com> 3180 S. 166th St. <Rick.MillerKILLspamLinux.org> New Berlin, WI 53151 USA +1 414 797 8000 x-228 -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAwUBMJ4nhWJrU1sdj28/AQEYnAP/T6kvbTMWZ/a660M6lcELEvJGnX0H5yN7 n+fo9uUOIdDIsfZpCsSsJI6ptedpcv6BC5RHO3/2KC8sdC2/Gz+0VWJIqed4Z257 TjWWK1AArlybGVuI8MG+QGjx+XYp+lN+QMBvcixTyB8ZVDN8n4+hnt/oIrnWO90y lVGQnuXdQS4= =MCyf -----END PGP SIGNATURE-----

you wrote: > -----BEGIN PGP SIGNED MESSAGE----- > > On Sat, 4 Nov 1995, Adrian Kennard wrote: > > >I wasn't to happy with the standard PIC assembler, so I have written an > >alternative version. Its primarily for 16C84 use. I have used it for a > >couple of programs and it seems to work okay. > > > >I don't know if anyone is interested in this. I can compile to 286 based DOS > >and uuencode, but its a bit long to post to the pic list. I could set up a > >mail responder to automatically email copies to people I suppose. > > I'm interested... especially if you're going to release the source-code! > Hopefully, you've written it in ANSI C so I can compile it under Linux!! > (PIC16C84 program-download code is already out there, somewhere...) > > Boy, I'd *love* it if I wouldn't have to keep DOS around for PIC development. A few people have asked this. I would rather wait until the source is a little more stable, until then its under my control. In the mean time I am attempting to get executables for :- Sun spark Linux 286 (anything else people want) I will also see if I can set up an ftp or web site for it (any offers?) I have ARM versions already as that's what I wrote it on <-: Yes, its ANSI C, but let me have you comments on the program (20 of you so far!) and I will make necessary improvements/fixes before releasing source. BTW, I am thinking of making a PIC programmer for use on Acorn platforms as well, unless anyone has one (<-:). -- _ (_) _| _ . _ _ Tel +44 973 222257 ( )(_|( |(_|| ) Fax UK 0500 222258 E&OE

you wrote: {Quote hidden}> -----BEGIN PGP SIGNED MESSAGE----- > > On Sat, 4 Nov 1995, Adrian Kennard wrote: > > >I wasn't to happy with the standard PIC assembler, so I have written an > >alternative version. Its primarily for 16C84 use. I have used it for a > >couple of programs and it seems to work okay. > > > >I don't know if anyone is interested in this. I can compile to 286 based DOS > >and uuencode, but its a bit long to post to the pic list. I could set up a > >mail responder to automatically email copies to people I suppose. > > I'm interested... especially if you're going to release the source-code! > Hopefully, you've written it in ANSI C so I can compile it under Linux!! > (PIC16C84 program-download code is already out there, somewhere...) > > Boy, I'd *love* it if I wouldn't have to keep DOS around for PIC development. > > Rick Miller, Design Engineer (and local "Internet Guy") > Digalog Systems, Inc. <.....rickKILLspam.....digalogsys.com> > 3180 S. 166th St. <EraseMERick.Millerspam_OUTTakeThisOuTLinux.org> > New Berlin, WI 53151 USA +1 414 797 8000 x-228 > > > -----BEGIN PGP SIGNATURE----- > Version: 2.6.2 > > iQCVAwUBMJ4nhWJrU1sdj28/AQEYnAP/T6kvbTMWZ/a660M6lcELEvJGnX0H5yN7 > n+fo9uUOIdDIsfZpCsSsJI6ptedpcv6BC5RHO3/2KC8sdC2/Gz+0VWJIqed4Z257 > TjWWK1AArlybGVuI8MG+QGjx+XYp+lN+QMBvcixTyB8ZVDN8n4+hnt/oIrnWO90y > lVGQnuXdQS4= > =MCyf > -----END PGP SIGNATURE----- > I am not keen to release source yet. The last thing I want is 1000 people all fixing bugs in my source code and emailing it back. It is marginally better if I hear of problems or improvements and fix them myself. Maybe I will release source when the code is a big more stable. In the mean time, a friend with a Linux box is compiling for me and Ill post you a copy. -- _ (_) _| _ . _ _ Tel +44 973 222257 ( )(_|( |(_|| ) Fax UK 0500 222258 E&OE

> On Sat, 4 Nov 1995, Adrian Kennard wrote: > > >I wasn't to happy with the standard PIC assembler, so I have written an > >alternative version. Its primarily for 16C84 use. I have used it for a > >couple of programs and it seems to work okay. > > > >I don't know if anyone is interested in this. I can compile to 286 based DOS > >and uuencode, but its a bit long to post to the pic list. I could set up a > >mail responder to automatically email copies to people I suppose. > > I'm interested... especially if you're going to release the source-code! > Hopefully, you've written it in ANSI C so I can compile it under Linux!! > (PIC16C84 program-download code is already out there, somewhere...) > > Boy, I'd *love* it if I wouldn't have to keep DOS around for PIC development. If you want a PIC assembler for Linux you might also want to check out pictools at ftp://nic.funet.fi/pub/microprocs/pic/pictools It includes an assembler and a few conversion tools between its own pictools format and intel16. I think I had to patch one line which caused a core dump with Linux but I have been using it for a few months now and am very satisfied. The only PIC program-download code for LINUX I know about is prog84 (also at nic.funet.fi). Please tell me if there are any others available. I would especially be interested in code for the simple serial port programmer. I only found the DOS version. Ralph ------------------------------------------------------------ Ralph Metzler rjkmspam_OUTthp.uni-koeln.de Institute for Theoretical Physics Cologne, Germany ============================================================