Hello, I just recently got a PicKit 3 and some of the new(ish)
PIC16F1503 microcontrollers. I have the PIC hooked up correctly -as
far as I can tell at least. Power, data, clock, etc. all are hooked up
to the programmer on a solderless breadboard. When it comes time to
program the MCU the programmer does not detect the device at all
(device ID 0x00), when I put another MCU [a PIC16f690] in its place it
works just fine. I've tried both LVP and normal programming modes in
the IDE [MPLABX] to no avail. Just a note: I don't have any pull
up/down resistors in place, but I don't believe their needed.
Since I'm rather new to this programmer I must be making some mistake,
if anyone has some tips or tricks to make this work it would be
greatly appreciated.
> Hello, I just recently got a PicKit 3 and some of the new(ish)
> PIC16F1503 microcontrollers. I have the PIC hooked up correctly -as
> far as I can tell at least. Power, data, clock, etc. all are hooked up
> to the programmer on a solderless breadboard. When it comes time to
> program the MCU the programmer does not detect the device at all
> (device ID 0x00), when I put another MCU [a PIC16f690] in its place it
> works just fine. I've tried both LVP and normal programming modes in
> the IDE [MPLABX] to no avail. Just a note: I don't have any pull
> up/down resistors in place, but I don't believe their needed.
>
> Since I'm rather new to this programmer I must be making some mistake,
> if anyone has some tips or tricks to make this work it would be
> greatly appreciated.
>
> --
> Jason White
At 05:03 PM 5/17/2012, Jason White wrote:
>Hello, I just recently got a PicKit 3 and some of the new(ish)
>PIC16F1503 microcontrollers. I have the PIC hooked up correctly -as
>far as I can tell at least. Power, data, clock, etc. all are hooked up
>to the programmer on a solderless breadboard. When it comes time to
>program the MCU the programmer does not detect the device at all
>(device ID 0x00), when I put another MCU [a PIC16f690] in its place it
>works just fine. I've tried both LVP and normal programming modes in
>the IDE [MPLABX] to no avail. Just a note: I don't have any pull
>up/down resistors in place, but I don't believe their needed.
>
>Since I'm rather new to this programmer I must be making some mistake,
>if anyone has some tips or tricks to make this work it would be
>greatly appreciated.
I would be tempted to pull the chip from the breadboard and just mini-hook clips to connect to its pins. Or: solder wires to a socket.
I suspect that you may be running into capacitive coupling between the CLK and DATA pins - some plastic breadboards have extremely high capacitance between the rows.
Regardless, it should take only a few minutes to try this out.
dwayne
PS - I am assuming that you didn't swap the clk & data pins on the chip.
> Hello, I just recently got a PicKit 3 and some of the new(ish)
> PIC16F1503 microcontrollers. I have the PIC hooked up correctly -as
> far as I can tell at least. Power, data, clock, etc. all are hooked up
> to the programmer on a solderless breadboard. When it comes time to
> program the MCU the programmer does not detect the device at all
> (device ID 0x00), when I put another MCU [a PIC16f690] in its place it
> works just fine. I've tried both LVP and normal programming modes in
> the IDE [MPLABX] to no avail. Just a note: I don't have any pull
> up/down resistors in place, but I don't believe their needed.
>
> Since I'm rather new to this programmer I must be making some mistake,
> if anyone has some tips or tricks to make this work it would be
> greatly appreciated.
On 5/17/2012 7:03 PM, Jason White wrote:
> Hello, I just recently got a PicKit 3 and some of the new(ish)
> PIC16F1503 microcontrollers. I have the PIC hooked up correctly -as
> far as I can tell at least. Power, data, clock, etc. all are hooked up
> to the programmer on a solderless breadboard
Do you have another 16F1503 chip that you can swap out ? Sometimes it can just be a bad chip. It doesn't happen often but it does happen. I had a dead 24X pic the other day and nothing I could do would make it work with the programmer, swapped it out and circuit works fine now.
Mark
gmail.com> wrote:
