gnupic: [gnupic] Article on Programming PICs in Linux
Subject:
Re: [gnupic] Article on Programming PICs in Linux
From:
####@####.####
Date:
21 Apr 2005 20:57:15 +0100
Message-Id: <33207.65.42.87.62.1114113432.squirrel@micahcarrick.com>
Martyn Welch wrote:
>-----BEGIN PGP SIGNED MESSAGE-----
>Hash: SHA1
>
>- ------ Original message ------
>On Thursday 21 Apr 2005 00:56, ####@####.#### wrote:
>
>>If any of you are new to programming PICs in Linux I've written an article
>>on getting started using gputils and gpsim based on my experiences the
>>last few months. Feedback would be great.
>>
>><a
>>href="http://www.micahcarrick.com/v2/content/view/5/4/">http://www.micahcar
>>rick.com/v2/content/view/5/4/</a>
>>
>>- Micah
>
>
>I've been programming Microcontrollers for quite a while now, however it's
>only very recently that I have been doing it entirely on Linux. I tend to
>program in C - that part was easy to sort out, there are both reasonable
>proprietary and free compilers available.
>
>The hardest part I found was finding a widely supported PIC programmer
that I
>could afford! At Uni I am spoilt for choice, though I can't substantiate
>paying for a PICStart Plus at home!
>
>Thus I have also written a few pages :-)
>
>http://ubicomp.lancs.ac.uk/~martyn/sdcc_linux/
>
>http://www.warpedlogic.co.uk/linux_pic_programming/
>
>Neither is as nicely done as yours yet, I was very impressed with gpsim, I
>knew of it's existence, never seen it. Does anyone know if it will work with
>the asm files produced by SDCC?
>
>I am currently working on getting a nice 2 layer masked and screen printed
>board produced, which is a slight variant on the jdm programmer, with a
>break-out board like Microchips ICD2. It works well with Picprog, though
is a
>little slow at times. I will provide schematics and board layouts (probably
>in eagle files) parts lists etc when I am sure it works! I might even do a
>run of boards if anyone is interested...
>
>Martyn
>
>- --
>Martyn Welch ####@####.####
>
>PGP Key : http://ubicomp.lancs.ac.uk/~martyn/pgpkey/
>-----BEGIN PGP SIGNATURE-----
>Version: GnuPG v1.2.4 (GNU/Linux)
>
>iD8DBQFCZ2vlQPzYXciChNcRAlCFAJ4iD3Pg4aXKbqslT7XrHsd+xoHNygCcDZJd
>mFUIITkjh4FwCA4oYE+5vjQ=
>=IF4s
>-----END PGP SIGNATURE-----
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: ####@####.####
>For additional commands, e-mail: ####@####.####
>
>
>
>
Nice articles. I never found those in all my "googling". I'll have to
read through them more... especially the SDCC article. I did use
PICC-Lite once, and although it was easy enough to use, it didn't generate
the debug info for use with gpsim... but then again, there is probably a
place to configure how it calls the assembler. not sure. I believe when
I was using gpsim before I had to use a -g argument to get the source code
browser but not anymore. I'm not entirely sure though.
Also, regarding programmers, I used the programmer built in to PikDev
before with my epic Plus, however, I no longer use KDE nor do I have a
parallel port. I'm now using a Kitsrus K 150 USB programmer and trying to
figure out how to get Rick Altherr's pp program to work. Once I get that
going I'm going to write a GUI for it in GTK and write an article on that
whole deal.
- Micah Carrick
http://www.micahcarrick.com
