I've done this two different ways.  I have a VC++ program the programs PICs
serially through the parallel port.  It erases the chip and then loads the
new code.

I have also used a bootloader which a small program that runs everytime the
PIC starts.  I have a VB program running and connected to the PIC through a
serial port.  When the VB program senses that the PIC is running, it starts
sending new code to it through the serial port, and the PIC essentially
reprograms itself.

If either of these methods will help you, let me know.  These programs were
written for work, so I can just send them to you, but I'll help with info
all I can.

Jim

jimm@servicemate.com

-----Original Message-----
From: pic microcontroller discussion list
[mailto:PICLIST@MITVMA.MIT.EDU]On Behalf Of Kev Pearce (kevp.com)
Sent: Wednesday, October 29, 2003 10:53
To: PICLIST@MITVMA.MIT.EDU
Subject: [PIC:] First Real PIC Project


Hi PICers,

Having made the move from the Basic Stamp II to straight PICs, I'm kind of
missing some of the BS2's features, namely dedicated programming pins,
dedicated debug output pins and a dedicated reset pin.

I would like to make my first PIC project 'field upgradeable'. By packaging
up the hex code into a windows .exe that uses COM1 to pump out serial data.
A VB app with a little test screen first would probably be the way to do it.

So does anyone out there do this?? I realise it means building into the
design effectively a PIC programmer. I'm sticking to a 12V source and 12Fxxx
PIC chips. I've googled around to try and find about diy pic serial
programmers but every return is a dedicated programmer board for sale either
built or in kit form. What I was really after is some circuit ideas to get
me started on it, being new to this PIC lark I'm not sure of the differences
in programmers between the EEPROM and Flash series PICs.

So anyone any ideas or websites that might help me. I'm not after circuits
just some pointers to get me going. I had thought of simply buying a few
programmer kits and using the parts but I'd rather understand it first!

This would also allow me to build a prototype board and then simply
re-programme new code into it, using dedicated pins, and know that the
perifery devices connect to it will not effect the programming. Or the
programming circuit effect the general working of the device!

Any ideas??

Thanks very much all


Kev/.

--
http://www.piclist.com hint: PICList Posts must start with ONE topic:
[PIC]:,[SX]:,[AVR]: ->uP ONLY! [EE]:,[OT]: ->Other [BUY]:,[AD]: ->Ads

--
http://www.piclist.com hint: PICList Posts must start with ONE topic:
[PIC]:,[SX]:,[AVR]: ->uP ONLY! [EE]:,[OT]: ->Other [BUY]:,[AD]: ->Ads