Shawn, make sure that you are using an MPLAB version of MPLAB 7.4 or later. The firmware that gets installed for the ICD2 before that point was incredibly buggy. I was getting the same foolishness. Once I installed 7.4, the ICD2 cleared up IMMEDIATELY and I've had no trouble since. I use two ICD2s and the Wong Mini-ICD2 and a Wong Full USB ICD2 (my favorite). Wong was the one that indicated that the MPLAB code for ICD2 was buggy before that point. I'm using WinXP with a very fast Intel processor. --Bob Shawn Wilton wrote: > OK, still having issues. I'm getting the ICD to recognize something. But > I'm getting this: > > Setting Vdd source to target > ICDWarn0020: Invalid target device id (expected=0x7E, read=0x1FF) > ICDWarn0044: Target has an invalid calibration memory value (0x3FFF). > Continue? > > I have pic12f675 set in both mplab and of course the chip is a 675. Ideas? > I've redone this darn cable atleast 12 times thinking I've done something > wrong, but I'm quite certain it is correct. > > > On 9/28/06, Shawn Wilton wrote: > >> OK, so I've been screwing around with this thing forever and I'm >> frustrated. I can't get it to recognize my 12f675 on my board (even though >> another programmer I have recognizes it just fine). So I said, OK, start >> with something we know should work (bypass the custom cables). So I plugged >> it in to the PICDEM2+ that I ordered with my ICD and it still doesn't >> recognize the device. Help. >> >> -- >> >> Shawn Wilton (b9 Systems) >> http://b9Systems.com <- New web page >> > > > > > -- http://www.piclist.com PIC/SX FAQ & list archive View/change your membership options at http://mailman.mit.edu/mailman/listinfo/piclist