part 1 959 bytes content-type:text/plain; format=flowedOK...I checked, and rechecked the cable and circuit, swapped to a 1K pup on
the Vpp pin, still it doesnt want to behave.
To verify the programming cable is good, I put a header on my other dev
board that has the RJ jack so I know all is well there, and proved the cable
is OK, as I figured (it ohmed out ok). This means back to the hardware....
So, attached is the schematic, in a word document. The difference between
the two target boards is the problem one is a plcc package, while the one
that is working is DIP. I do have a target board I can test this on that is
also PLCC, so just to eliminate one more thing.
>One other fact I forgot to mention
>Target Vdd looks good now, using the ICD2 to power the PIC, reads 4.84 in
>both boards, but the 'bad' target Vpp is at 6.77 rather than 12.xx
Have you connected to the correct pins? You mentioned that the one that does
not work is a PLCC while the one that works is DIP. I believe the pin
numbers are different for the programming pins, and what you are saying here
suggests that you are trying to power the whole chip from the VPP voltage,
through protection diodes on the pin.
Sorry on the lousy schematic, I copied it from a PDF then into word. I
printed it and thought, oh not so good on the resolution.
Some other results from last night....that points to some wierd hardware
setup on the board that I can't seem to find...yet.
I took my toys and went home, where I plugged the target chip into another
board that had a PLCC socket and RJ11 interface, and of course it worked
fine, eliminating the possiblitly that the new board was somehow killing the
chips (a pretty far fetched idea, but can't overlook anything)
I brought in today my old ICD1 interface so I'm going to see what it might
tell me, but probably the same thing.
I am running the system under USB, have tried with and without the wallwart
supply, no difference
As suggested, perhaps the pinouts are wrong, but of course that was the
first thing I checked.