Searching \ for '[PIC] ICD2' in subject line. ()
Make payments with PayPal - it's fast, free and secure! Help us get a faster server
FAQ page: www.piclist.com/techref/microchip/devprogs.htm?key=icd
Search entire site for: 'ICD2'.

Exact match. Not showing close matches.
PICList Thread
'[PIC] ICD2'
2005\05\23@040139 by Paul van der Linden

picon face
Hi,
I'm just starting with pic-microcontrollers, and have ordered the icd2
from microchip.
But it isn't working, I always get this error after programming the
device ( I have selected the icd2 as debugger):
ICD0083: Target not in debug mode, unable to perform operation
Can anyone help me, what do I wrong?
Paul

2005\05\23@040519 by Michael Rigby-Jones

picon face


>-----Original Message-----
>From: spam_OUTpiclist-bouncesTakeThisOuTspammit.edu [.....piclist-bouncesKILLspamspam@spam@mit.edu]
>Sent: 23 May 2005 09:01
>To: Microcontroller discussion list - Public.
>Subject: [PIC] ICD2
>
>
>Hi,
>I'm just starting with pic-microcontrollers, and have ordered the icd2
>from microchip.
>But it isn't working, I always get this error after programming the
>device ( I have selected the icd2 as debugger):
>ICD0083: Target not in debug mode, unable to perform operation
>Can anyone help me, what do I wrong? Paul


What device are you trying to debug?

Regards

Mike

=======================================================================
This e-mail is intended for the person it is addressed to only. The
information contained in it may be confidential and/or protected by
law. If you are not the intended recipient of this message, you must
not make any use of this information, or copy or show it to any
person. Please contact us immediately to tell us that you have
received this e-mail, and return the original to us. Any use,
forwarding, printing or copying of this message is strictly prohibited.
No part of this message can be considered a request for goods or
services.
=======================================================================

2005\05\23@041546 by Chen Xiao Fan

face
flavicon
face
Which chip are you using? What is the supply voltage?
ICD2 has quite a lot of restrictions as a programmer
and a debugger. For quite some low pin-count device
(eg. PIC12F629/675, 16F630/676, 16F627A/628A/648A),
you will even need an header for debugging.

Also please check the connection. The biggest problem
I have with ICD2 is actually the connection. ICD2 is very
picky in this aspect.

Xiaofan

-----Original Message-----
From: Paul van der Linden [pvdl1984spamKILLspamxs4all.nl]
Sent: Monday, May 23, 2005 4:01 PM
To: Microcontroller discussion list - Public.
Subject: [PIC] ICD2


Hi,
I'm just starting with pic-microcontrollers, and have ordered the icd2
from microchip.
But it isn't working, I always get this error after programming the
device ( I have selected the icd2 as debugger):
ICD0083: Target not in debug mode, unable to perform operation
Can anyone help me, what do I wrong?
Paul

2005\05\23@043622 by Paul van der Linden

picon face
Michael Rigby-Jones wrote:

{Quote hidden}

the 18F4550

2005\05\23@043937 by Paul van der Linden

picon face
Chen Xiao Fan wrote:

>Which chip are you using? What is the supply voltage?
>ICD2 has quite a lot of restrictions as a programmer
>and a debugger. For quite some low pin-count device
>(eg. PIC12F629/675, 16F630/676, 16F627A/628A/648A),
>you will even need an header for debugging.
>
>Also please check the connection. The biggest problem
>I have with ICD2 is actually the connection. ICD2 is very
>picky in this aspect.
>
>Xiaofan
>
>{Original Message removed}

2005\05\23@045941 by Lindy Mayfield

flavicon
face
I'm quite new to PICS, but as I recall this happened to me at first when the oscillator settings were incorrect or the wrong oscillator was being used.  Check the config to see which one you are using.  Maybe even try the internal one to see if that changes things.

Or better, post the config settings.

> {Original Message removed}

2005\05\23@081027 by Mike Hord

picon face
> I'm just starting with pic-microcontrollers, and have ordered the icd2
> from microchip.
> But it isn't working, I always get this error after programming the
> device ( I have selected the icd2 as debugger):
> ICD0083: Target not in debug mode, unable to perform operation
> Can anyone help me, what do I wrong?
> Paul

Did you set the debug configuration bit?  That might cause it to be
finnicky.

Mike H.

2005\05\23@081533 by olin_piclist

face picon face
Paul van der Linden wrote:
> I'm using the 18F4550.
> Programming, reading, erasing, enz is working.

None of these require a clock.  Also, did you reserve the resources needed
by the ICD2 in the code?


*****************************************************************
Embed Inc, embedded system specialists in Littleton Massachusetts
(978) 742-9014, http://www.embedinc.com

2005\05\23@090406 by Howard Winter

face
flavicon
picon face
Paul,

On Mon, 23 May 2005 10:01:07 +0200, Paul van der Linden wrote:

> Hi,
> I'm just starting with pic-microcontrollers, and have ordered the icd2
> from microchip.
> But it isn't working, I always get this error after programming the
> device ( I have selected the icd2 as debugger):
> ICD0083: Target not in debug mode, unable to perform operation
> Can anyone help me, what do I wrong?

Yes, the ICD2 can act in two modes, as a Programmer or as a Debugger - the latter needs a PIC that supports
debug mode, and it looks like you're just trying to program it.

The correct procedure to start up is from the top menu to select "Configure" then "Select Device" and choose
the PIC you're using, then "Programmer" then "Select Programmer" from the top menu, then "MPLAB ICD2" and
you'll be set up properly to use it as a programmer.  Don't touch "Debugger" unless you want to use it that
way and know how to do so!  :-)

Cheers,

4
Howard Winter
St.Albans, England


2005\05\23@122801 by Dave Turner

picon face
Hey,

Make sure in your config bits/settings, you have the oscillator set to
output.  If the PIC doesn't output the clock signal, the ICD throws
that error.  Also, ensure you programmed the chip in debug mode -
don't just program it in programmer mode, and then switch to debug and
click run - in debug mode, click the program button, making sure the
ICD2 isn't selected as programmer, but debugger.  When programmed in
debug mode, the ICD2 programs a special piece of code called a debug
executive - this sits there while your program is running, and stop it
, reads variables, etc.  In programmer mode, the debug executive isn't
programmed - programmer mode is designed for final copies, in which
you won't want debug things taking up space.  Also, if this still
doesn't fix it, try double clicking on the blue text in the output
window - on the line with the error, the error number should be in
blue - double click it to open the help file, on the right page for
that error.

Finally, with some microchips, they don't support the ICD2 in the
normal version - with these chips, you have to get the -ICD2 version.
I'm not quite sure which chips these are, so check before you go and
buy some -ICD2 versions.

On 5/23/05, Howard Winter <HDRWspamspam_OUTh2org.demon.co.uk> wrote:
{Quote hidden}

> -

2005\05\23@124436 by Paul van der Linden

picon face
Howard Winter wrote:

{Quote hidden}

I was testing if it is running if I selected the icd2 as programmer, and
then apply power.
It looks like it's not running.
If I understand it good this will light a led on the RB0 port:

       LIST P=18F4550, R=DEC

       #include "P18F4550.INC"

       CLRF  TRISB
       BSF     PORTB, 0
       END

2005\05\23@132234 by Paul van der Linden

picon face
>        LIST P=18F4550, R=DEC
>
>        #include "P18F4550.INC"
>
>        CLRF  TRISB
>        BSF     PORTB, 0
>        END


Ok, if I program the device, this is working, so it runs, only debugging
isn't working.
I've these configuration bits:
http://members.lycos.nl/pvdl1984/icd2.html

Log of the icd2:
Connecting to MPLAB ICD 2
...Connected
Setting Vdd source to target
Target Device PIC18F4550 found, revision = a3
...Reading ICD Product ID
Running ICD Self Test
...Passed
MPLAB ICD 2 Ready
Programming Target...
...Validating configuration fields
...Erasing Part
...Programming Program Memory (0x0 - 0x3F)
...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
ICD0083: Target not in debug mode, unable to perform operation
MPLAB ICD 2 Ready

Is there anything wrong with the settings?

2005\05\23@133011 by Paul van der Linden

picon face
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.
Paul

2005\05\23@133153 by Dave Turner

picon face
Well, it's probably the oscillator - I'm not sure, but the ICD2
probably can't run from a USB clock.  Try using either the internal or
external RC, or an external crystal - Crystals are only really needed
for anything that uses a clock, etc - RCs are useless for clocks, but
fine for everything else.

On 5/23/05, Paul van der Linden <@spam@pvdl1984KILLspamspamxs4all.nl> wrote:
{Quote hidden}

> -

2005\05\23@134837 by olin_piclist

face picon face
Paul van der Linden 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.

That's the way it's supposed to work.  It only runs with the ICD2 if in
debug mode, and then the ICD2 is required.  If the ICD2 is being used as a
programmer, then it must be disconnected for the target to run.


*****************************************************************
Embed Inc, embedded system specialists in Littleton Massachusetts
(978) 742-9014, http://www.embedinc.com

2005\05\23@135119 by Dave Turner

picon face
When programming, you have to click the release from reset button to
allow the program to run - the PIC stays in reset for programming
untill you tell the ICD2 to take !MCLR high.

Or, something in your circuit could be stopping the ICD2 controlling !MCLR.

On 5/23/05, Paul van der Linden <KILLspampvdl1984KILLspamspamxs4all.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.
> Paul
>
> -

2005\05\23@140233 by Michael Rathbun

flavicon
face
On Mon, 23 May 2005 19:29:30 +0200, Paul van der Linden
<RemoveMEpvdl1984TakeThisOuTspamxs4all.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.

2005\05\23@140838 by Dave Turner

picon face
It shouldn't have to be disconnected.  IF it is connected though, two
pins on the chip will be unavailable, because the ICD2 holds them low.
It should still run though.

On 5/23/05, Olin Lathrop <spamBeGoneolin_piclistspamBeGonespamembedinc.com> wrote:
{Quote hidden}

> -

2005\05\23@142425 by Paul van der Linden

picon face
Michael Rathbun wrote:

>On Mon, 23 May 2005 19:29:30 +0200, Paul van der Linden
><TakeThisOuTpvdl1984EraseMEspamspam_OUTxs4all.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

2005\05\23@143440 by Dave Turner

picon face
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 <RemoveMEpvdl1984spamTakeThisOuTxs4all.nl> wrote:
{Quote hidden}

> -

2005\05\23@150501 by Andre Abelian

flavicon
face
Speaking of ICD what's the different between CCS ICD and
Microchip's ICD2. I called ccs tech support they said
CCS icd is faster then microchip's icd2. Also do you use CCS IDE ?
or it is better to use MPLAB and link it to ccs compiler ?

Andre





{Original Message removed}

2005\05\23@151315 by Paul van der Linden

picon face
Dave Turner wrote:

{Quote hidden}

>>-

2005\05\23@152216 by Dave Turner

picon face
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 <RemoveMEpvdl1984spam_OUTspamKILLspamxs4all.nl> wrote:
{Quote hidden}

2005\05\23@152430 by Gerhard Fiedler

picon face
Olin Lathrop wrote:

>> 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.

Did you try the Release MCLR command (or something like that)?

> That's the way it's supposed to work.  It only runs with the ICD2 if in
> debug mode, and then the ICD2 is required.  If the ICD2 is being used as
> a programmer, then it must be disconnected for the target to run.

This is not correct. You can release the MCLR from within MPLAB, and don't
have to disconnect the ICD2 (even when running the ICD2 as programmer).

Gerhard

2005\05\23@174157 by Paul van der Linden

picon face
Dave Turner wrote:

{Quote hidden}

2005\05\23@182337 by Paul James E.

picon face

Probably a moot point, but have you set the check box to have the debug
code load into the part when you program it?   Just a thought.

                                                  Regards,

                                                    Jim



{Quote hidden}

2005\05\23@184828 by Paul van der Linden

picon face
I don't see a checkbox anywhere, I checked by reading it, and only saw
my own code, does that say the debug code isn't programmed? How do I let
the debug code be programmed?
Paul James E. wrote:

{Quote hidden}

>

2005\05\24@063946 by Gerhard Fiedler

picon face
Paul van der Linden wrote:

>> Probably a moot point, but have you set the check box to have the debug
>> code load into the part when you program it?   Just a thought.

> I don't see a checkbox anywhere, I checked by reading it, and only saw my
> own code, does that say the debug code isn't programmed? How do I let
> the debug code be programmed?

I think MPLAB does that automatically, just as it doesn't let you handle
the ICD configuration flag manually in debugger mode (it sets it
automatically).

One other thing: the ICD2 as debugger requires the MCLR pin to be MCLR, not
GPIO. Some chips allow this to be configured in the configuration bits. But
MPLAB should warn you if this is set incorrectly.

[There is at least one datasheet out there that describes the wrong
polarity for this bit (18F2431), but the MPLAB configuration and the
include files that come with MPASM are correct IIRC.]

Maybe too obvious: in the Debugger | Settings, the Status and Power tabs
look all good?

Gerhard

2005\05\24@081701 by WH Tan

flavicon
face
Hello,
Disable "Dedicated ICD port" setting. If you're using a DIP part,
alternate ICD pins are not available. Those pins only exist on TQFP
part, and if you're using this part, the ICD connection is no longer
using RB7, RB6 etc. Check the datasheet under "Special features of uC"

Hope this helps.
WH Tan


{Original Message removed}

2005\05\24@144407 by Paul van der Linden

picon face
WH Tan wrote:

>Hello,
>Disable "Dedicated ICD port" setting. If you're using a DIP part,
>alternate ICD pins are not available. Those pins only exist on TQFP
>part, and if you're using this part, the ICD connection is no longer
>using RB7, RB6 etc. Check the datasheet under "Special features of uC"
>
>Hope this helps.
>WH Tan
>
>
>{Original Message removed}


'[PIC] ICD2'
2009\10\01@114703 by Manu Abraham
picon face
Hi list,

I have been using a ICD2 clone quite successfully along with a 16F72
and a 18F4550 respectively. Recently i tried a 16F877A (40 pin) on the
ICD2 add on card, but seems that the 877 pin was connected the same as
the 16F72 (28pin). After using the 877, it seems that the ICD2 doesn't
detect the 16F72 either, which shows up a dialog box stating
ICDWarn0020: Invalid target device id (expected=0x5, read=0x0). A
similar message results for the 18F4550 even when the connector is
setup properly. I have tried with a brand new 16F72 as well as a
18F4550 resulting in the same. Any idea what could be the cause ?

In MPLAB: Programmer->Settings->Run Self Test shows Pass, which i
guess, implies that the ICD2 self test is working fine. Another thing
what i tried was measuring the voltage across the PIC while the
connecting and it shows 4.72V. Any idea as to what's happening ?

Thanks,
Manu

2009\10\01@133020 by Manu Abraham

picon face
On Thu, Oct 1, 2009 at 7:47 PM, Manu Abraham <TakeThisOuTabraham.manuKILLspamspamspamgmail.com> wrote:
> Hi list,
>
> I have been using a ICD2 clone quite successfully along with a 16F72
> and a 18F4550 respectively. Recently i tried a 16F877A (40 pin) on the
> ICD2 add on card, but seems that the 877 pin was connected the same as
> the 16F72 (28pin). After using the 877, it seems that the ICD2 doesn't
> detect the 16F72 either, which shows up a dialog box stating
> ICDWarn0020: Invalid target device id (expected=0x5, read=0x0). A
> similar message results for the 18F4550 even when the connector is
> setup properly. I have tried with a brand new 16F72 as well as a
> 18F4550 resulting in the same. Any idea what could be the cause ?
>
> In MPLAB: Programmer->Settings->Run Self Test shows Pass, which i
> guess, implies that the ICD2 self test is working fine. Another thing
> what i tried was measuring the voltage across the PIC while the
> connecting and it shows 4.72V. Any idea as to what's happening ?
>


Lo, a couple of reboots of Windows Vista and all starts to work again.
The very first read from the 16F72 after the noise it read back 1FF,
on trying again, got things back to normal again. Things are much back
to normal again, with no idea as to what happened. Anyway sorry about
all the noise.

Regards,
Manu

More... (looser matching)
- Last day of these posts
- In 2009 , 2010 only
- Today
- New search...