Trying to debug with ICD2 and EB006 Multiprogrammer

[Mind Buzz]

Hello All,

I searched for this topic, but didn't see any answers, so here it goes.

I have been using my EB006 PIC multiprogrammer for some time, programming 16F818s, with no issues, works great!

Now I am creating another project, which requires a 18F4331, and of course with the new chipset, the archetecture is quiet different than the 16F818, and most likely I have some pretty sever programming errors in it, as it is not doing some of the simplest task. Right now, all I have the chip doing is incrementing a 7-segment display, when I press a button on one of the input channels. So I invested in a ICD2, since the eBlocks documentation stated that it worked with this device, so that I could step through the code, to find where I am screwing up.

But when I Build All, with the Debug setting set, then try to program the eBlock, which has the 18F4331 on it, it complains that I am trying to program a release platform with a debug build, do I want to rebuild? So I press the "No" button.

Then I select ICD2 as the debugger, and then press the "Step-Into" button, to start the party. and this is what I get for the output:

Auto-connect not enabled - Not connecting (Try enabling auto-connect on the ICD2 settings pages.)
Connecting to MPLAB ICD 2
...Connected
Setting Vdd source to target
Target Device PIC18F4331 found, revision = Rev 0x2
...Reading ICD Product ID
Running ICD Self Test
...Passed
MPLAB ICD 2 ready for next operation
ICDWarn0015: Program memory has changed since last program operation. Continue with Debug operation?
Stepping Target
ICD0083: Debug: Unable to enter Debug mode. Please double click this message for more information.
ICD0082: Failed MPLAP ICD 2 operation.
ICD0082: Failed MPLAP ICD 2 operation.
ICD0082:

Then the Busy light is on the ICD 2, and the MPLAB hangs.

Any suggestions??

[Benj]

Hello

Not come across this problem before. It might be worth your while updating the firmware on the ICD2. Microchip should be able to provide you with more support on their FAQ pages.