Re: [Usbpicprog-technical] PIC16F876A fail to program

[Frans S. <fra...@gm...>]

Ok, the difference is that the usbpicprog programmer has 470 Ohm 
resistors in series. If you don't use 3.3V devices, you can replace them 
with 100 Ohm. That will probably fix your problem.

Kind regards,

Frans Schreuder

On 04/18/2012 04:18 PM, Alexandre Rosa wrote:
> Thanks Frans,
>
> I figured out the problem, in 876A project PGD and PGC pins were 
> shared with an lcd bus lines so this should cause some interference in 
> programming. What is strange is that PICKIT3  do the job with no 
> problem. Any way thanks a lot.
>
> On Wed, Apr 18, 2012 at 5:12 AM, Frans Schreuder 
> <fra...@gm... <mailto:fra...@gm...>> wrote:
>
>     Hello,
>
>     The two devices use exactly the same algorithm and are also
>     electrical identical. I have programmed the 876A many times and
>     never experienced this behaviour.
>     Have you checked:
>
>       * your hardware voltages
>       * all the connections to the 876A
>       * that the PGM pin was connected to ground
>
>     This could also be bad luck, you can try to request a free sample
>     from microchip to get yourself a new 16F876A
>
>     Kind regards,
>
>     Frans Schreuder
>
>
>     On 04/17/2012 04:24 PM, Alexandre Rosa wrote:
>>     Hey
>>
>>     I have build a USBPICPROG through-hole version board and want to
>>     thank you for the good job in this project.
>>
>>     I was able to program a 16F877A without any problem but with a
>>     16F876A the programming has failed.
>>
>>     16/4/2012 13:50:32: Erasing before programming...
>>     16/4/2012 13:50:32: Erase OK
>>     16/4/2012 13:50:32: Programming the code area of the PIC...
>>     16/4/2012 13:51:05: Write Code memory OK
>>     16/4/2012 13:51:05: Programming the data area of the PIC...
>>     16/4/2012 13:51:05: Write Data memory OK
>>     16/4/2012 13:51:05: Verifying all areas of the PIC...
>>     16/4/2012 13:51:06: Verify code failed at 0x0. Read: 0xFF,
>>     Expected: 0x0A
>>     16/4/2012 13:51:06: Programming configuration area of the PIC...
>>     16/4/2012 13:51:06: Error programming config memory
>>     16/4/2012 13:51:06: Operations completed with errors/warnings
>>
>>     In this case the 16F876A had been previous programmed with a
>>     PICKIT3 and was erased or bad programmed by USBPICPROG and did
>>     not work after this try.
>>
>>     I try an external 5V power supply to do the job of USB BUS supply
>>     with no results.
>>
>>     Any suggestions ?
>>
>>
>>     ------------------------------------------------------------------------------
>>     Better than sec? Nothing is better than sec when it comes to
>>     monitoring Big Data applications. Try Boundary one-second
>>     resolution app monitoring today. Free.
>>     http://p.sf.net/sfu/Boundary-dev2dev
>>
>>
>>     _______________________________________________
>>     Usbpicprog-technical mailing list
>>     Usb...@li...  <mailto:Usb...@li...>
>>     https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical
>
>     ------------------------------------------------------------------------------
>     Better than sec? Nothing is better than sec when it comes to
>     monitoring Big Data applications. Try Boundary one-second
>     resolution app monitoring today. Free.
>     http://p.sf.net/sfu/Boundary-dev2dev
>     _______________________________________________
>     Usbpicprog-technical mailing list
>     Usb...@li...
>     <mailto:Usb...@li...>
>     https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical
>
>
>
>
> ------------------------------------------------------------------------------
> Better than sec? Nothing is better than sec when it comes to
> monitoring Big Data applications. Try Boundary one-second
> resolution app monitoring today. Free.
> http://p.sf.net/sfu/Boundary-dev2dev
>
>
> _______________________________________________
> Usbpicprog-technical mailing list
> Usb...@li...
> https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical