On Monday I received my package from dipmicro and futurelec together, including everything needed for assembling both Inchworm and Firefly. The assembly was pretty good (Bill, please widen the holes for the ZIF, and maybe change the layout of the transistors to a striaght line, but other than that, pretty easy).
Setting up the debugger took a few tries, but in the end, I have successfully ran both of the test 16f88 tutor programs (the one that does nothing but loop so you can see the button changes on the watch'ed PORTB, and the blinky88).
Now I want to get to some other projects and burn some hex files for either the 12f629 or 12f675. This has met with no success. In fact, it has met with no success programming any chip in the ZIFF socket. I'm hoping this is a simple oversight of mine somewhere, but Im stumped.
My problem goes like this:
I want to program a chip, let's start with one of the 8 pin jobs (12f629 and 12f675; tested with 3 different 629 chips, and one 675 chip), so I set the DIPs on the firefly to all off, except for the last '8/18 pins' switch. Firefly is connected with short ribbon cable to the Inchworm, Inchworm is powered froma 12v wall-wart, green lights on both boards. 8 pin chip is inserted into ZIF with pin 1 of the PIC at pin 11 of the ZIF. (pin 2 at pin 12, 3 @ 13, 4 @ 14, and whatever the opposite is- no, I dont think I put it in 180 degrees from correct
Inside MPLAB, Configure->Set device ->12f629. Select programmer as ICD2, and Connect.
The result is always identical to this, (except the expected device id, but 0x0 is always the byte read)
After failing wiht the 8 pins, I also tried a 16F88 (18 pin) and a 18F4455 (40 pin), changing the number of pin's DIP as appropriate and running through the same steps as above; all read 0x0 bytes, and if the chip used an OSCCAL, readding 0x0 for it as well when connecting. Yes, MPLAB downloaded a new operating system when the chips were changed to different packages.
To make matters even worse, if I disable all of the DIP's but the Tutor one, it connects and identifies the 16F88 in the tutor circuit just fine. I have been leaving the tutor 16f88 in the IC socket, assuming it would not interfere with programming; is this wrong?
I disconnected the ribbon cable from the firefly, and used a multimeter to test continuity from all of the pin pairs to the matching 8 pin connections on the ZIF; all 5 were present.
Any help would be greatly appreciated.
Setting up the debugger took a few tries, but in the end, I have successfully ran both of the test 16f88 tutor programs (the one that does nothing but loop so you can see the button changes on the watch'ed PORTB, and the blinky88).
Now I want to get to some other projects and burn some hex files for either the 12f629 or 12f675. This has met with no success. In fact, it has met with no success programming any chip in the ZIFF socket. I'm hoping this is a simple oversight of mine somewhere, but Im stumped.
My problem goes like this:
I want to program a chip, let's start with one of the 8 pin jobs (12f629 and 12f675; tested with 3 different 629 chips, and one 675 chip), so I set the DIPs on the firefly to all off, except for the last '8/18 pins' switch. Firefly is connected with short ribbon cable to the Inchworm, Inchworm is powered froma 12v wall-wart, green lights on both boards. 8 pin chip is inserted into ZIF with pin 1 of the PIC at pin 11 of the ZIF. (pin 2 at pin 12, 3 @ 13, 4 @ 14, and whatever the opposite is- no, I dont think I put it in 180 degrees from correct
Inside MPLAB, Configure->Set device ->12f629. Select programmer as ICD2, and Connect.
The result is always identical to this, (except the expected device id, but 0x0 is always the byte read)
Code:
Connecting to MPLAB ICD 2
...Connected
Setting Vdd source to target
ICDWarn0020: Invalid target device id (expected=0x91, read=0x0)
...Reading ICD Product ID
Running ICD Self Test
...Passed
...Download Operating System Succeeded
Setting Vdd source to target
ICDWarn0020: Invalid target device id (expected=0x91, read=0x0)
...Reading ICD Product ID
Running ICD Self Test
...Passed
MPLAB ICD 2 Ready
After failing wiht the 8 pins, I also tried a 16F88 (18 pin) and a 18F4455 (40 pin), changing the number of pin's DIP as appropriate and running through the same steps as above; all read 0x0 bytes, and if the chip used an OSCCAL, readding 0x0 for it as well when connecting. Yes, MPLAB downloaded a new operating system when the chips were changed to different packages.
To make matters even worse, if I disable all of the DIP's but the Tutor one, it connects and identifies the 16F88 in the tutor circuit just fine. I have been leaving the tutor 16f88 in the IC socket, assuming it would not interfere with programming; is this wrong?
I disconnected the ribbon cable from the firefly, and used a multimeter to test continuity from all of the pin pairs to the matching 8 pin connections on the ZIF; all 5 were present.
Any help would be greatly appreciated.