>Have you setup OSCCON?  Check it out in the datasheet.  Make sure your
>OSCCON settings match your oscillator settings.
>
>On 5/23/05, Paul van der Linden <EraseMEpvdl1984EraseMETakeThisOuTxs4all.nl> wrote:
>  
>
>>Dave Turner wrote:
>>
>>    
>>
>>>Yeh, I think if the software can't connect to the debug executive
>>>(Which I think is because of your USB clock), it pauses the chip, or
>>>puts it back into reset.  I recomend trying setting the config bit for
>>>oscillator to internal.  Also, to change the speed, you can use the
>>>OSCCON register.  If this works, you know that the ICD2 not supporting
>>>usb oscillator is the problem.
>>>
>>>On 5/23/05, Paul van der Linden <KILLspampvdl1984TakeThisOuTspamBeGonexs4all.nl> wrote:
>>>
>>>
>>>      
>>>
>>>>Michael Rathbun wrote:
>>>>
>>>>
>>>>
>>>>        
>>>>
>>>>>On Mon, 23 May 2005 19:29:30 +0200, Paul van der Linden
>>>>><spampvdl1984RemoveMExs4all.nl> wrote:
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>          
>>>>>
>>>>>>I think I've found the problem, but not the solution:
>>>>>>When I program it with the icd2(without debug executive), it only runs
>>>>>>if I disconnect the icd2.
>>>>>>I've found out that if the icd2 is connected, mclr is always low. I
>>>>>>think there is a fault in my circuit, but I can't find it.
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>            
>>>>>>
>>>>>This sounds like normal behaviour.  If you want the loaded program to run
>>>>>after the download with the ICD still connected, you need to click the
>>>>>"release from reset" button in the IDE.
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>          
>>>>>
>>>>ok, that works,
>>>>but I can't get an high on mclr in debug mode of the icd2
>>>>
>>>>--