PICKit2 Programming Problem
mcki0127
for a project that was completed a long time ago and I'm now trying to
update it. The programmer correctly IDs the device and I can load the
hex file and program it. When I verify it, I get a verification
successful message. However, when I plug the device into my working
circuit (verified with a previously working MCU), it won't do
anything.
All of the I/O pins read 0V even if I try to drive them high. I've
tried programming 4 other 16F77s and a 16F84A all with the same result
- successful programming and verification, yet they don't work in a
circuit. I've tried programming with a PICKit2 clone from Sure
Electronics and with the one from Microchip, but get the same results
with each. If the MCUs are bad, I wouldn't expect the verify to
pass. I've read about the possible need of adding an external
powersupply in the event the USB cable can't supply the proper
programming voltage. Could that be the problem, and how would I go
about doing that? I have the programmer hooked up to a board with a
DIP ZIF socket. Any ideas?
Thanks,
Steve
mcki0127
Xiaofan Chen
>
> I am trying to program a PIC16F77 using a PICKit2 programmer. This is
> for a project that was completed a long time ago and I'm now trying to
> update it. The programmer correctly IDs the device and I can load the
> hex file and program it. When I verify it, I get a verification
> successful message. However, when I plug the device into my working
> circuit (verified with a previously working MCU), it won't do
> anything.
>
You'd better ask this kind of question in Microchip Forum.
http://forum.microchip.com/tt.aspx?forumid=15
This means PICkit 2 is ok but your hex is not ok. Probably
you do not have the proper configuration bits in the hex file.
If you need to get further assistance, ask in the Microchip Forum.
Xiaofan
Daniel Turner
based on info from the PIC's datasheet (MCLR resistor value, crystal,
etc)...if it works then there is something different between the new
PICs and the original MCU. Try to reduce the problem down to the
simplest components. Your project could require different code than
you are using (maybe it was documented wrong?), there could be a
problem with the circuit that doesn't affect the old MCU, maybe the
pinout isn't the same, maybe all your pics are dead, maybe the old mcu
is an older version of the same PIC with some undocumented difference,
there are a million other 'maybe's. Reduce, reduce, reduce. Test the
simplest things first. Sorry for the rambling...
--
-Daniel
KD5UZZ
www.w5yj.org
mcki0127
On Oct 18, 8:38 pm, "Daniel Turner" <danielttur...@gmail.com> wrote:
> Can you build a circuit to test a PIC you've just programmed? built it
> based on info from the PIC's datasheet (MCLR resistor value, crystal,
> etc)...if it works then there is something different between the new
> PICs and the original MCU. Try to reduce the problem down to the
> simplest components. Your project could require different code than
> you are using (maybe it was documented wrong?), there could be a
> problem with the circuit that doesn't affect the old MCU, maybe the
> pinout isn't the same, maybe all your pics are dead, maybe the old mcu
> is an older version of the same PIC with some undocumented difference,
> there are a million other 'maybe's. Reduce, reduce, reduce. Test the
> simplest things first. Sorry for the rambling...
>
> On 10/18/07, mcki0127 <mcki0...@hotmail.com> wrote:
>
>
>
>
>
>
>
> > I am trying to program a PIC16F77 using a PICKit2 programmer. This is
> > for a project that was completed a long time ago and I'm now trying to
> > update it. The programmer correctly IDs the device and I can load the
> > hex file and program it. When I verify it, I get a verification
> > successful message. However, when I plug the device into my working
> > circuit (verified with a previously working MCU), it won't do
> > anything.
>
> > All of the I/O pins read 0V even if I try to drive them high. I've
> > tried programming 4 other 16F77s and a 16F84A all with the same result
> > - successful programming and verification, yet they don't work in a
> > circuit. I've tried programming with a PICKit2 clone from Sure
> > Electronics and with the one from Microchip, but get the same results
> > with each. If the MCUs are bad, I wouldn't expect the verify to
> > pass. I've read about the possible need of adding an external
> > powersupply in the event the USB cable can't supply the proper
> > programming voltage. Could that be the problem, and how would I go
> > about doing that? I have the programmer hooked up to a board with a
> > DIP ZIF socket. Any ideas?
>
> > Thanks,
> > Steve
>
> --
> -Daniel
> KD5UZZwww.w5yj.org- Hide quoted text -
>
> - Show quoted text -
I have set up a small circuit for the 16F84A with only the essentials,
and written a very simple program to control one IO pin. I've also
tried different configuration settings, but I get the same results.
But, I'll resume this in the Microchip forum.
Thanks.
Mark Rages
> I have set up a small circuit for the 16F84A with only the essentials,
> and written a very simple program to control one IO pin. I've also
> tried different configuration settings, but I get the same results.
> But, I'll resume this in the Microchip forum.
>
You could give try pyk instead of pk2. A different set of bugs.
Or post your source code.
Regards,
Mark
markrages@gmail
--
Mark Rages, Engineer
Midwest Telecine LLC
mark...@midwesttelecine.com
soliton
>
> You could give try pyk instead of pk2. A different set of bugs.
>
> Or post your source code.
And may be post your circuit too. Some times we forget to connect MCLR
pin through 10K of resistor to VDD, especially since a lot of PIC
devices now support programmable MCLR pin as I/O :) And on the
firmware side, we forget to disable watchdog, and never kick the dog
in our application, so the dog will kick us instead on the 'brain' :D
--
soliton
------------------------------------
Diskusi di http://phimega.com/forums