Re: Learning PIC on the job

On Mon, Aug 15, 2005 at 04:44:01PM +0800, Chen Xiao Fan wrote:
> Wisp628 is a much better recomendation for programmers under 
> both Linux and Windows than JDM/Tait type.

Unfortunately you have the chicken/egg problem if you don't
have a programmer.

As I'm sure everyone well knows, I think programmers of all types
are way overrated. Personally I recommend a cheap code dumper
(like my Tait style Trivial Programmers) coupled with a bootloader
most any day. Unless one is using the ICD features, I find very
little advantage to a traditional programmer at all. BTW it
obviates the need for "moving chip from programmer to target"
as specified below.

My most successful and complete projects were implemented on a 
16F877 using Wouters WLoader and Woj's linwload.

BAJ
> Regards,
> Xiaofan
> 
> -----Original Message-----
> From: Matthijs van Henten [mailto:[email protected]]
> Sent: Saturday, August 13, 2005 9:16 PM
> To: [email protected]
> Subject: Re: [gnupic] Learning PIC on the job
> 
> 
> I have been 'learning' pic on the job -
> I started out with a jdm programmer and destroyed a couple of pics while 
> moving the chip in and out of my cirquit.
> Also I found it to be quite slow. i use a wisp628 kit now. in serial 
> programming, I just made another connector to my cirquit. I use a 
> dataswitcher  to switch between the cirquit serial output and it's 
> programming port and basically made a small experimentation board around 
> a 16f88 and 16f628 this way. I soldered nice colored wires to all of the 
> left over ports ( A0 to A5 and some of port B ) and stick them in to 
> breadboards to connect to other periferals.
> 
> compiling -> uploading to the pic -> reading debug output from serial 
> port takes 30 seconds, versus a cycle of 3 t o5 minutes and the risk of 
> breaking a leg off my pic sometimes.
> the wisp kit can be build yourself or ordered but quite cheap.
> 
> cheers!
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]