>
>Hello Igor,
>
>I am no expert on the details of PIC programming, but I checked
>the device include file that comes with my EPIC programmer, and
>it shows exactly the same configuration word for 'C84, 'F84, and
>'F84A, so "parameters" is probably not your problem. From .INC
>files:
>
>                                        ; *** DEVICE Device Definitions
>PIC16F83        equ     50010400h       ; 14-Bit, 512 Code, 64 EE, ID = 0
>PIC16F84        equ     50020401h       ; 14-Bit,  1K Code, 64 EE, ID = 1
>PIC16F84A       equ     50020401h       ; 14-Bit,  1K Code, 64 EE, ID = 1
>
>                                        ; *** DEVICE Device Definitions
>PIC16C84        equ     50020401h       ; 14-Bit, 1K Code, 64 EE, ID = 1
>
>
>regards,
>- Dan Michaels

>
>Actually Dan,
>
>The config word is different between the 16C84 and the others. The above
>information does not include any config word information that I can see.
>Like any good programmer software the EPIC is relying on the correct
>config values being provided via the HEX file and ultimately via the
>assembler/compiler. It is in these software tools that differences in the
>config word should, and are defined.
>

>Jim Robertson wrote:
>>At 10:43 AM 02/10/00 -0400, you wrote:
>>>Igor wrote:
>>>I've purchased the pic16f84A (A is important!) and I've spent
>>>couple of hours to get programmed the chip (I have dtait
>>>lpt programmer and no problems with lot of pic16f84, sw I use is
>>>wpicprog32 from nigel goodwin v 1.2 and 1.22).
>...........
>>
>>Actually Dan,
>>
>>The config word is different between the 16C84 and the others. The above
>>information does not include any config word information that I can see.
>>Like any good programmer software the EPIC is relying on the correct
>>config values being provided via the HEX file and ultimately via the
>>assembler/compiler. It is in these software tools that differences in the
>>config word should, and are defined.
>>
>
>
>Ooops, you are correct, Jim. 'C84 is different. However, it does
>look like the 'F84 and 'F84A have the same config word, so Igor should
>not have to change parameters between the two. Correct? And his problem
>is probably somewhere else.

> At 11:51 PM 02/10/00 -0400, you wrote:
> >Jim Robertson wrote:
> >>At 10:43 AM 02/10/00 -0400, you wrote:
> >>>Igor wrote:
> >>>I've purchased the pic16f84A (A is important!) and I've spent
> >>>couple of hours to get programmed the chip (I have dtait
> >>>lpt programmer and no problems with lot of pic16f84, sw I use is
> >>>wpicprog32 from nigel goodwin v 1.2 and 1.22).
> >...........
> >>
> >>Actually Dan,
> >>
> >>The config word is different between the 16C84 and the others. The above
> >>information does not include any config word information that I can see.
> >>Like any good programmer software the EPIC is relying on the correct
> >>config values being provided via the HEX file and ultimately via the
> >>assembler/compiler. It is in these software tools that differences in

> >>config word should, and are defined.
> >>
> >
> >
> >Ooops, you are correct, Jim. 'C84 is different. However, it does
> >look like the 'F84 and 'F84A have the same config word, so Igor should
> >not have to change parameters between the two. Correct? And his problem
> >is probably somewhere else.
>
> Yes and yes. I think Igor has a problem in the electrical side, maybe
> the PSU slew rate is too high or it is overshooting causing latch-up.
>
> -Jim
>
> >
> >- danM
> >
> >--
> >http://www.piclist.com#nomail Going offline? Don't AutoReply us!
> >use spamBeGonelistservspamBeGonemitvma.mit.edu?body=SET%20PICList%20DIGEST> > >
> >
> >
> Regards,
>
> Jim Robertson
> NEWFOUND ELECTRONICS
> Email: TakeThisOuTnewfoundEraseMEspam_OUTpipeline.com.au
> http://www.new-elect.com
> MPLAB compatible PIC programmers.
>