Searching \ for '[PIC] ICD2: "Target Not In Debug Mode Error"' 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: "Target Not In Debug Mode Error"'.

Exact match. Not showing close matches.
PICList Thread
'[PIC] ICD2: "Target Not In Debug Mode Error"'
2004\09\19@015134 by Bob Axtell

face picon face
I'm stumped. I've never had this error before unless the clock was
broken (it isn't).

The PIC (PIC16LF88) runs perfectly at 3.5V, will program my
"wink" test fragment from the ICD2 as a programmer, and when
selected as debugger, all seems OK except for the error. (NO, I
don't have ICD2 selected at both programmer and debugger).

Neither PGC, MCLR, or PGD is connected to anything except the
debugger. Well, MCLR has a 47K pullup on it only to VDD.

I haven't tried to run the PIC at 5V because it has some 3.6V max
peripherals attached.

The PIC runs flawlessly for the wink test.

Any ideas, fellow PIClisters?

--Bob

--
Note: Attachments must be sent to
spam_OUTattachTakeThisOuTspamengineer.cotse.net, and
MAY delay replies to this message.
      520-219-2363




--
Note: Attachments must be sent to
.....attachKILLspamspam@spam@engineer.cotse.net, and
MAY delay replies to this message.
       520-219-2363

_______________________________________________
http://www.piclist.com
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist

2004\09\19@031940 by redtock8

flavicon
face
I'm using ICD2 right now and had the same problem.
I'm using f877a. I had the wrong osc set and had to check
power from ICD2 in the setup.
Al


{Original Message removed}

2004\09\19@032403 by Harold Hallikainen

face picon face
I get that error if I have code protect set on any flash or if I have
table write disabled on any flash or the config bits (I'm used to working
with the PIC18F series).

Good luck!

Harold


{Quote hidden}

--
FCC Rules Online at http://www.hallikainen.com
_______________________________________________
http://www.piclist.com
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist

2004\09\19@083004 by Gerhard Fiedler

picon face
> The PIC (PIC16LF88) runs perfectly at 3.5V, will program my
> "wink" test fragment from the ICD2 as a programmer, and when
> selected as debugger, all seems OK except for the error. (NO, I
> don't have ICD2 selected at both programmer and debugger).
>
> Neither PGC, MCLR, or PGD is connected to anything except the
> debugger. Well, MCLR has a 47K pullup on it only to VDD.

FWIW, we currently have the same problem here (same chip, same setup, same
symptoms)... no solution yet.

Gerhard
_______________________________________________
http://www.piclist.com
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist

2004\09\19@124818 by Bob Axtell

face picon face
Should we take it up with Microchip? who do I complain to?

Heaven forbid, could the LF88 NOT have a debug mode..?

Anybody else EVER worked with the LF88? I notice that the
TSS0P20 version of the LF88 is very unavailable. Problems,
maybe?


--Bob

Gerhard Fiedler wrote:

{Quote hidden}

--
Note: Attachments must be sent to
EraseMEattachspam_OUTspamTakeThisOuTengineer.cotse.net, and
MAY delay replies to this message.
       520-219-2363

_______________________________________________
http://www.piclist.com
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist

2004\09\19@130055 by Ishaan Dalal

flavicon
face
Bob Axtell wrote:

 > The PIC (PIC16LF88) runs perfectly at 3.5V, will program my
> "wink" test fragment from the ICD2 as a programmer, and when
> selected as debugger, all seems OK except for the error. (NO, I
> don't have ICD2 selected at both programmer and debugger).

Well, apart from the regular gotchas (clock, code protect, etc.), the
one time I had this problem persistently, I had to have the ICD2
replaced by Microchip. The tech support guy, after walking me through
the troubleshooting steps, deiced that the output buffers on my ICD2 had
blown.

Do you have another ICD2 around you could use to test this?

-Ishaan
_______________________________________________
http://www.piclist.com
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist

2004\09\19@135405 by redtock8

flavicon
face
I found this in the ICD2 HELP

All Except PIC16F877A

 a.. Program memory not enhanced flash. Cannot program in low voltage mode
(Vdd<4.5V.) See device programming specification for more information.
{Original Message removed}

2004\09\19@175753 by Bob Axtell

face picon face
Well, I am able to program and then run the test program perfectly with
the ICD2 at 3.5V; I just can't put it into
debug mode.

You might be right, though, I just got through with a major F88 project
at 5V using the ICD2, no problems.
BUT- if the ICD2 doesn't work at 3.5V, I have a serious problem, as
everything in MY forseeable future
is 3.5V.

I'm going ahead, hobbling along using the ICD2 as a programmer, and
putting my own debug tools inside
(Morse code beeper, RS232 serial port dump, etc). Sure makes things alot
harder.

Where was that note? On Microchip help forum?

--Bob

redtock8@dxtron wrote:

> I found this in the ICD2 HELP
>
> All Except PIC16F877A
>
>  a.. Program memory not enhanced flash. Cannot program in low voltage
> mode (Vdd<4.5V.) See device programming specification for more
> information.
> {Original Message removed}

2004\09\19@184409 by Ken Pergola

flavicon
face

Bob Axtell wrote:

> BUT - if the ICD 2 doesn't work at 3.5V, I have a serious problem, as
> everything in MY foreseeable future is 3.5V.

Hi Bob,

If you ever code protect the PIC16F87/PIC16F88 and then want to reverse the
code protection bits in the future, the *only* way to do such is through a
chip erase, and Vdd must be in the range of 4.5 volts to 5.5 volts to
initiate a chip erase. This means that your board has to be designed to
handle the application of this higher Vdd to accomplish this (without
adversely affecting your 3.5 volt devices in the process).

A lot of flash PICs at the moment have this constraint. Take a look at the
programming specifications for more details.

Best regards,

Ken Pergola


_______________________________________________
http://www.piclist.com
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist

2004\09\20@000201 by Bob Axtell

face picon face
Hmmm. I never did set the chip protect bits, but I did design the PCB so
that the LF88 (only) can
take 5V for being programmed by a normal programmer. Think if I simply
execute a simple full chip
erase with my K128 that it might start running right?

--Bob

Ken Pergola wrote:

{Quote hidden}

--
Note: Attachments must be sent to
attachspamspam_OUTengineer.cotse.net, and
MAY delay replies to this message.
       520-219-2363

_______________________________________________
http://www.piclist.com
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist

2004\09\20@005142 by Ken Pergola

flavicon
face

Bob Axtell wrote:

> Think if I simply execute a simple full chip
> erase with my K128 that it might start running right?

Hi Bob,

It's worth a try. Could you post the configuration bit settings you are
using? Maybe that information will might shed some light on something?

Also, you are having a problem with the Microchip ICD 2, and not on the ICD
2 clone, correct? Or are you seeing this problem with the ICD 2 clone as
well?

Best regards,

Ken Pergola



_______________________________________________
http://www.piclist.com
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist

2004\09\20@010047 by Ken Pergola

flavicon
face

Hi Bob,

Perhaps a long shot since you have previously stated that nothing else is
connected to the PGD and PGC pins, but does this situation apply to you?:

>From PIC16F87/88 Errata:
------------------------
Note: The Timer1 oscillator shares the T1OSI and T1OSO pins with the PGD and
PGC pins used for programming and debugging. When using the Timer1
oscillator, In-Circuit Serial Programming (ICSP) may not function correctly
(high voltage or low voltage), or the In-Circuit Debugger (ICD) may not
communicate with the controller. As a result of using either ICSP or ICD
operation, the Timer1 crystal may be damaged.
If ICSP or ICD operations are required, the crystal should be disconnected
from the circuit (disconnect either lead), or installed after programming.
The oscillator loading capacitors may remain in-circuit during ICSP or ICD
operation.

Best regards,

Ken Pergola


_______________________________________________
http://www.piclist.com
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist

2004\09\20@045131 by Howard Winter

face
flavicon
picon face
Ken,

Sorry to fray the thread...

On Mon, 20 Sep 2004 01:00:45 -0400, Ken Pergola wrote:

>...<
> >From PIC16F87/88 Errata:
> ------------------------
> Note: The Timer1 oscillator shares the T1OSI and T1OSO
pins with the PGD and
> PGC pins used for programming and debugging. When
using the Timer1
> oscillator, In-Circuit Serial Programming (ICSP) may
not function correctly
> (high voltage or low voltage), or the In-Circuit
Debugger (ICD) may not
> communicate with the controller.

Does this mean that you can't use Timer 1 at all, or
just not with an external crystal?  

I'm not very familiar with the various uses of timers,
but I believe that they normally use the main crystal's
waveform for timing, so I hope this still works without
upsetting ICSP or ICD...

Cheers,

Howard Winter
St.Albans, England


_______________________________________________
http://www.piclist.com
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist

2004\09\20@051113 by Jan-Erik Soderholm

face picon face
Howard Winter wrote :

> > Note: The Timer1 oscillator shares the T1OSI and T1OSO
> > pins with the PGD and PGC pins...

> Does this mean that you can't use Timer 1 at all,..

No.

> or  just not with an external crystal?  

Yes.

> I believe that they [timers] normally use the main crystal's
> waveform for timing,

What is "normal" varies, of course, but that setup isn't the
setup the errata sheet was talking about.

Best Regards,
Jan-Erik.
_______________________________________________
http://www.piclist.com
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist

2004\09\20@071251 by Gerhard Fiedler

picon face
> It's worth a try. Could you post the configuration bit settings you are
> using? Maybe that information will might shed some light on something?

This is in my source (HiTech PICC):

 __CONFIG(           // PIC configuration bits:
   HS                // (HS, RC, XT, LP) high speed crystal
   & WDTDIS          // (WDTDIS, WDTEN) watch dog timer disabled
   & PWRTEN          // (PWRTEN, PWRTDIS) power up timer enabled
   & BOREN           // (BOREN, BORDIS) brown out reset enabled
   & LVPDIS          // (LVPEN, LVPDIS) low voltage programming disabled
   & UNPROTECT       // (DPROT, DUNPROT) EEPROM data unprotected
   & UNPROTECT       // (WRTEN, WRTDIS) flash write disabled
   & DEBUGDIS        // (DEBUGEN, DEBUGDIS) debugger disabled
 );

AFAIK, MPLAB overrides the debug bit.

> Also, you are having a problem with the Microchip ICD 2, and not on the ICD
> 2 clone, correct? Or are you seeing this problem with the ICD 2 clone as
> well?

We are using a clone. And that same clone is working fine on another board
with an 18F458 (5V).

Gerhard
_______________________________________________
http://www.piclist.com
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist

2004\09\20@095115 by Bob Axtell

face picon face
Gerhard Fiedler wrote:

>>It's worth a try. Could you post the configuration bit settings you are
>>using? Maybe that information will might shed some light on something?
>>    
>>
>
>This is in my source (HiTech PICC):
>
>  __CONFIG(           // PIC configuration bits:
>    HS                // (HS, RC, XT, LP) high speed crystal
>    & WDTDIS          // (WDTDIS, WDTEN) watch dog timer disabled
>    & PWRTEN          // (PWRTEN, PWRTDIS) power up timer enabled
>    & BOREN           // (BOREN, BORDIS) brown out reset enabled
>    & LVPDIS          // (LVPEN, LVPDIS) low voltage programming disabled
>    & UNPROTECT       // (DPROT, DUNPROT) EEPROM data unprotected
>    & UNPROTECT       // (WRTEN, WRTDIS) flash write disabled
>    & DEBUGDIS        // (DEBUGEN, DEBUGDIS) debugger disabled
>  );
>
>  
>
Mine is just like Gerhard's (ABOVE) except that the BROWNOUT is DIS and
the debugger is enabled
DEBUGEN .


{Quote hidden}

I am using a clone for this, which is normally LESS cranky and easier to
wire up than  the regular ICD2,
which I own as well. I guess I'll wire up the MC unit and try it, but
I've never seen any difference before.

Actually, using my Morse debug unit I am 50% done with the code already...

--Bob



{Quote hidden}

--
Note: Attachments must be sent to
@spam@attachKILLspamspamengineer.cotse.net, and
MAY delay replies to this message.
       520-219-2363

_______________________________________________
http://www.piclist.com
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist

2004\09\20@103407 by Ken Pergola

flavicon
face

Howard Winter wrote:

> Does this mean that you can't use Timer 1 at all, or
> just not with an external crystal?  

Hi Howard,

The errata is applicable when you use the Timer 1 *oscillator*.

Best regards,

Ken Pergola



_______________________________________________
http://www.piclist.com
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist

2004\09\22@095240 by alan smith

picon face
Also....switching back and forth between program and
debug mode sometimes 'fixes' issues.

--- Harold Hallikainen <KILLspamharoldKILLspamspamhallikainen.com> wrote:

{Quote hidden}

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
_______________________________________________
http://www.piclist.com
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist

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