On Wed, Aug 11, 2010 at 12:54 PM, Todd Lyons wrote: > 1. From what I can tell, to use c as the programming language, I have > to be using a PIC18 or higher, and with PIC16 or lower, I must use > assembly. =A0Yea or nay? nay. You can use C on the 16F parts. But practically, the pic16 instruction set is not designed for C use, and pic18 parts are pennies more. So go with pic18 or better unless you are making a thousand copies. > 2. In my project, I will need ... I think your circuit could also be built on one of those solderless breadboards. Making a board isn't that hard, so that's what I do. > 3. I'm interested in using piklab and gpasm/gplink under Linux, but am > willing to use the MPLAB IDE if I have to. =A0My limitations are that I > just don't know Windows like I know Linux. =A0Any recommendations or > experiences would be welcome. I've no experience with piklab. gpasm and gplink work fine. They use the same syntax as the official Microchip tools, so read the Microchip documents to learn it. I've used make+emacs+gpasm for 16f projects. Works great. Also look at SDCC, which is a Free compiler for small devices including PIC= .. Before you get too wedded to PICs, you should look at AVR/Arduino and MSP430. Both have good gcc-based toolchains in Linux. > Part of my personality is that I'm impatient. =A0I want to do things and > make big dreams now! =A0So I'm working on learning first, and not just > trying random stuff :-) (which is what I typically do). A little patience will serve you well as you learn this stuff. Regards, Mark markrages@gmail --=20 Mark Rages, Engineer Midwest Telecine LLC markrages@midwesttelecine.com --=20 http://www.piclist.com PIC/SX FAQ & list archive View/change your membership options at http://mailman.mit.edu/mailman/listinfo/piclist .