> Harold Hallikainen wrote:
>> OK, MPLAB 7.41 did not fix the problem. I guess use of another
>> programmer
>> (like PM3) would be ok, but how am I supposed to debug stuff without the
>> ICD-2? This used to work fine! I really count on the use of the ICD-2
>> for
>> debug. It's a whole lot easier than just staring at the code trying to
>> see
>> what's wrong (or even running it through the simulator, which doesn't
>> simulate all our hardware). This is really bad if we can't get the ICD
>> running! Again, until last week, it worked great! I dunno what changed.
>> I
>> had not done an MPLAB upgrade in a while (I was running 7.31), so the
>> ICD
>> firmware should not have changed. Now I'm running 7.41 in the hopes that
>>
> oops. You did NOT upgrade to the downloadable firmware provided for the
> ICD2 I/O by MPLAB7.4?
> That's where the error is.
>
> --Bob

The only ICD-2 file I see after doing the upgrade to MPLAB 7.4 is:

C:\Program Files\Microchip\MPLAB IDE\ICD2\ICD05010309.hex

Is that not the current version? If not, what is, and where can I get it?

Also, when I do an erase, that doesn't work.

Here's what I get:

MPLAB ICD 2 Ready
Downloading Operating System
Connecting to MPLAB ICD 2
...Connected
Setting Vdd source to target
Target Device PIC18F6722 found, revision = Rev 0x0
...Reading ICD Product ID
Running ICD Self Test
...Passed
...Download Operating System Succeeded
MPLAB ICD 2 Ready
Erasing Target Device...
...Erase Succeeded
MPLAB ICD 2 Ready
Blank Checking...
...Program Memory
ICD0161: Verify failed (MemType = Program, Address = 0x0, Expected Val =
0xFFFF, Val Read = 0x0)
...Device not blank
MPLAB ICD 2 Ready


Ideas?

Thanks!

Harold

-- 
FCC Rules Updated Daily at http://www.hallikainen.com - Advertising
opportunities available!
-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist