Here's the log from the 18F4620 and 10F206, with my notes after ======
Note that all errors (apart from the invalid OSCAL value), are corrected 
by pushing the ICSP cable deeper than just the "click" of the RJ11 cable.



======Everything working - program chip using ICD2 as debugger.
02-Oct-2006, 16:47:06

MPLAB ICD 2 Ready
Programming Target...
...Validating configuration fields
...Erasing Part
...Programming Program Memory (0x0 - 0x47F)
...Loading DebugExecutive
...Programming DebugExecutive
...Programming Debug Vector
...Programming RSBUG
Verifying...
...Program Memory
...Debug Executive
...Debug Vector
...Verify Succeeded
Programming Configuration Bits
.. Config Memory
Verifying configuration memory...
...Verify Succeeded
Connecting to debug executive
...Programming succeeded
02-Oct-2006, 16:47:24

======Gently pulling the RJ11 ICSP connector so that it is not seated 
quite as deeply in the ICD2, then try program...
MPLAB ICD 2 Ready
Programming Target...
ICDWarn0052: MPLAB ICD 2 cannot validate a target device. Please make 
sure that the target device is connected and properly powered. Select 
"OK" to continue, or "CANCEL" to abort the operation
...Validating configuration fields
...Erasing Part
...Programming Program Memory (0x0 - 0x47F)
...Loading DebugExecutive
...Programming DebugExecutive
...Programming Debug Vector
...Programming RSBUG
Verifying...
ICDWarn0052: MPLAB ICD 2 cannot validate a target device. Please make 
sure that the target device is connected and properly powered. Select 
"OK" to continue, or "CANCEL" to abort the operation
...Program Memory
ICD0161: Verify failed (MemType = Program, Address = 0x0, Expected Val = 
0xEF1C, Val Read = 0x0)
ICD0275:  Programming failed.
MPLAB ICD 2 Ready

======Clicking the "Reset and connect to ICD2" toolbar button
Connecting to MPLAB ICD 2
...Connected
Setting Vdd source to MPLAB ICD 2
ICDWarn0020: Invalid target device id (expected=0x60, read=0x0)
...Reading ICD Product ID
Running ICD Self Test
...Passed
MPLAB ICD 2 Ready

======Pressing the "Run" Debug button
ICD0083: Debug:  Unable to enter debug mode.  Please double click this 
message for more information.
Running Target
ICD0083: Debug:  Unable to enter debug mode.  Please double click this 
message for more information.
ICD0069: Debug:  Unable to run target
MPLAB ICD 2 Ready

======Running the "Self Test" button from the ICD2 Settings dialogue.
Running ICD Self Test
...Passed


======
======
======Then, with the 10F206....
======
======

Connecting to MPLAB ICD 2
...Connected
ICDWarn0030: MPLAB ICD2 is about to download a new operating system.  If 
MPLAB IDE is just starting, it will appear to "hang" at the splash 
screen.  Please be patient.  MPLAB IDE will finish it's intialization 
after the OS is downloaded.  (Note:  You may wish to select to ignore 
this warning in the future.)
Downloading Operating System
Connecting to MPLAB ICD 2
...Connected
Setting Vdd source to MPLAB ICD 2
ICDWarn0044:  Target has an invalid calibration memory value (0xFFF).  
Continue?
...Reading ICD Product ID
Running ICD Self Test
...Passed
...Download Operating System Succeeded
Setting Vdd source to MPLAB ICD 2
ICDWarn0044:  Target has an invalid calibration memory value (0xFFF).  
Continue?
...Reading ICD Product ID
Running ICD Self Test
...Passed
MPLAB ICD 2 Ready

======Programming the chip while the connector is "deep".
Programming Target...
ICDWarn0044:  Target has an invalid calibration memory value (0xFFF).  
Continue?
...Validating configuration fields
...Erasing Part
...Programming Program Memory (0x0 - 0xFF)
Verifying...
...Program Memory
...Verify Succeeded
Programming Configuration Bits
.. Config Memory
Verifying configuration memory...
...Verify Succeeded
...Programming succeeded
02-Oct-2006, 16:55:55

MPLAB ICD 2 Ready


======Programming the chip when it is *not* deep.
Programming Target...
ICDWarn0052: MPLAB ICD 2 cannot validate a target device. Please make 
sure that the target device is connected and properly powered. Select 
"OK" to continue, or "CANCEL" to abort the operation
ICDWarn0044:  Target has an invalid calibration memory value (0x0).  
Continue?
...Validating configuration fields
...Erasing Part
...Programming Program Memory (0x0 - 0xFF)
Verifying...
ICDWarn0052: MPLAB ICD 2 cannot validate a target device. Please make 
sure that the target device is connected and properly powered. Select 
"OK" to continue, or "CANCEL" to abort the operation
...Program Memory
ICD0161: Verify failed (MemType = Program, Address = 0x0, Expected Val = 
0x25, Val Read = 0x0)
ICD0275:  Programming failed.
MPLAB ICD 2 Ready


======Clicking the "Reset and connect to ICD2" toolbar button
Connecting to MPLAB ICD 2
...Connected
Setting Vdd source to MPLAB ICD 2
ICDWarn0044:  Target has an invalid calibration memory value (0x0).  
Continue?
...Reading ICD Product ID
Running ICD Self Test
...Passed
MPLAB ICD 2 Ready

======Re-seating the RJ11 connector and Clicking the "Reset and connect 
to ICD2" toolbar button again (note change in calibration value error)
Connecting to MPLAB ICD 2
...Connected
Setting Vdd source to MPLAB ICD 2
ICDWarn0044:  Target has an invalid calibration memory value (0xFFF).  
Continue?
...Reading ICD Product ID
Running ICD Self Test
...Passed
MPLAB ICD 2 Ready


Rolf

Rolf wrote:
> Yes. All the time. With a 10F206 I was getting "Invalid OSCAL value" 
> messages when programming. With 18F2320 and 18F4620 I was getting other 
> funny messages, but the self-test always passed. When I get home I will 
> capture some of the messages.....
>
> Rolf
>
> Shawn Wilton wrote:
>   
>> Were your self-tests passing in mplab?
>>
>>
>> On 10/2/06, Rolf <learr@rogers.com> wrote:
>>   
>>     
>>> Shawn Wilton wrote:
>>>     
>>>       
>
>
>   

-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist