All of lore.kernel.org
 help / color / mirror / Atom feed
From: Frank Terhaar-Yonkers <fty@cisco.com>
To: Phil <phil@spiderweb.com.au>
Cc: linux-hams@vger.kernel.org
Subject: Re: PIC programming question
Date: Wed, 08 Jan 2003 08:04:24 -0500	[thread overview]
Message-ID: <3E1C21D8.9040200@cisco.com> (raw)
In-Reply-To: <200301062005.06383.phil@spiderweb.com.au>

Phil,

I bought a cheap (hooks up to parallel port) programmer from:
	http://www.dontronics.com/prod.html
It and the PICALL software are like USD$65 assembled.  Works with nearly 
any PIC chip.
Also, check out "mplab" which is a free assembly language dev 
environment available from www.microchip.com.
If you are doing a lot of fooling around and testing, buy a couple of 
PICs that are eeprom based.  Erase them with a high-intensity UV light.
Cheaper in the long run than the burn once, throw aways.

cheers,

- Frank


Phil wrote:
> Hello All,
> 
> I'd to try my hand at PIC programming and the projects that I have in mind are 
> amateur radio related so I suppose this question is not off topic.
> 
> I have some utilities (gputils) that will create the hex code, however I'm 
> wondering what other people use to actually program the PIC.
> 
> An Internet search didn't reveal very many programmers for Linux. One 
> interesting project is called ponyprog2000. The hardware is more complex than 
> a typical programmer that operates under MS Windows but it's probably more 
> versatile. The software appears to be easy enough to use.
> 
> Does anyone have a favorite PIC programmer? My only interest at the moment is 
> to be able to program PIC 16F84 and 16F876 chips.
> 


-- 
  \\\\////\\\\////\\\\\////\\\\\////\\\\////\\\\////
  Frank Terhaar-Yonkers      W4FTY   TRA 8325/L2
  Cisco Systems, Inc.
  NSITE - Pineview Building - RTP
  7025 Kit Creek Road  PO Box 14987
  Research Triangle Park,  North Carolina  27709
  fty@cisco.com   voice(919)392-2101 fx(919)392-4833


  reply	other threads:[~2003-01-08 13:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-07  4:30 PIC programming question Phil
2003-01-08 13:04 ` Frank Terhaar-Yonkers [this message]
2003-01-08 13:23 ` Tomi Manninen
2003-01-08 20:54 ` Nuno Miguel Fernandes Sucena Almeida
2003-01-09  9:38 ` Wilbert Knol
     [not found] <E51999353E6CF54E856A3193EF0686CC34F9D9@actmail>
2003-01-08  0:48 ` Joshua Hayworth

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3E1C21D8.9040200@cisco.com \
    --to=fty@cisco.com \
    --cc=linux-hams@vger.kernel.org \
    --cc=phil@spiderweb.com.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.