Post by thread:c2c compiler and gpasm

I'm trying to set up to work in a Linux environment. It seems the best combination is the c2c compiler and gpasm, but I'm having some trouble. I guess my first question is, in a Linux environment, is this in fact the way to go? If not, what? If so, where are the best places to get these two? I'm trying to compile one of the examples that came with c2c, ex1.c. I compile like so: c2c ex1.c this works and produces an output file called ex1.asm which contains the line: include "p16c84.inc" This file was not included with my c2c distribution, so I tried the version from mplab but when I assembled it like so: gpasm ex1.asm I got all kinds of errors. Before I waste much more time on this, is this the best way to go? Thanks, Michael Shiloh

Michael Shiloh wrote: {Quote hidden}> > I'm trying to set up to work in a Linux environment. It seems the best > combination is the c2c compiler and gpasm, but I'm having some trouble. > > I guess my first question is, in a Linux environment, is this in fact > the way to go? If not, what? If so, where are the best places to get > these two? > > I'm trying to compile one of the examples that came with c2c, ex1.c. > I compile like so: > > c2c ex1.c > > this works and produces an output file called ex1.asm which contains the > line: > > include "p16c84.inc" > > This file was not included with my c2c distribution, so I tried the version > from mplab but when I assembled it like so: > > gpasm ex1.asm > > I got all kinds of errors. > > Before I waste much more time on this, is this the best way to go? Michael, I can't answer whether or not this the best way to go, but I can tell you how to get the include file. First of all, gpasm can not legally redistribute the microchip include files that come with mplab. However, as a user you may download mplab and get the files yourself. If this is too much of a pain in the ass, then you can download gpsim (the gnupic simulator) and use the very similar include file "p16c84.inc". If you use the microchip include files, then you'll have to be careful with case sensitivity. There's the case sensitivity switch '-c' that will make it work. Scott

Scott Dattalo kindly answered: >Michael Shiloh wrote: >> >> I'm trying to set up to work in a Linux environment. It seems the best >> combination is the c2c compiler and gpasm, but I'm having some trouble. >> >> <snip snip> > >Michael, > >If you use the microchip include files, then you'll have to be careful >with case sensitivity. There's the case sensitivity switch '-c' that >will make it work. That did it. Thanks! (I already had the files from MPLAB) Unfortunately my programmer is at home so I can't test this until later tonight. Maybe I'll install gpsim so I can test it at work! Thanks again, Michael Shiloh

Michael Shiloh wrote: > I'm trying to set up to work in a Linux environment. It seems the best > combination is the c2c compiler and gpasm, but I'm having some > trouble. Apart from c2c, this is the way I go. Also use emacs with a PIC specific ASM colour mode, CVS for the source repository, and make for building and burning. Also do the burns from a laptop connected by ethernet to my main development machine ... the Makefile causes the "rcp" remote copy of the .hex file to the burning laptop and uses "rsh" to start the burn. Where did you get c2c from? Free? -- James Cameron (spam_OUTquozlTakeThisOuTus.netrek.org) Linux, Firewalls, OpenVMS, Software Engineering, CGI, HTTP, X, C, FORTH, COBOL, BASIC, DCL, csh, bash, ksh, sh, Electronics, Microcontrollers, Disability Engineering, Netrek, Bicycles, Pedant, Farming, Home Control, Remote Area Power, Greek Scholar, Tenor Vocalist, Church Sound, Husband. "Specialisation is for insects." -- Robert Heinlein.

James Cameron wrote: >Michael Shiloh wrote: >> I'm trying to set up to work in a Linux environment. It seems the best >> combination is the c2c compiler and gpasm, but I'm having some >> trouble. I have since found my problem and can now compile C and assemble it completely on my Linux box. However, I still need to go to Windoze to do the actual burn, as my programmer is a PicStart and I understand there is no way to control it except through Mplab which does not run on Linux.... > >Apart from c2c, this is the way I go. > >Also use emacs with a PIC specific ASM colour mode, CVS for the source >repository, and make for building and burning. Also do the burns from a >laptop connected by ethernet to my main development machine ... the >Makefile causes the "rcp" remote copy of the .hex file to the burning >laptop and uses "rsh" to start the burn. Sounds like a good idea. What is your laptop running? What programmer are you using? >Where did you get c2c from? Free? Yep: http://sca.enlace.com.mx/c2c/c2c/c.html Michael Shiloh

Michael Shiloh wrote: > Sounds like a good idea. What is your laptop running? What programmer > are you using? Laptop runs Linux. Programmer software from the following source ... http://www.tatoosh.com/nexus/picpgmr.shtml http://www.tatoosh.com/nexus/linux/picprg.2.2.tar.gz ... but it's not GPL, so I'll probably implement my own. I have already coded up modifications to do 12C509, and I've tested it. Programmer board is a Tait design, either the Dontronics or the Kitsrus implementations work fine for me. -- James Cameron (.....quozlKILLspam@spam@us.netrek.org) Linux, Firewalls, OpenVMS, Software Engineering, CGI, HTTP, X, C, FORTH, COBOL, BASIC, DCL, csh, bash, ksh, sh, Electronics, Microcontrollers, Disability Engineering, Netrek, Bicycles, Pedant, Farming, Home Control, Remote Area Power, Greek Scholar, Tenor Vocalist, Church Sound, Husband. "Specialisation is for insects." -- Robert Heinlein.