Searching \ for '[PIC] Trouble with ICD2 + adaptor board (AC162050)' 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: 'Trouble with ICD2 + adaptor board (AC162050)'.

Exact match. Not showing close matches.
PICList Thread
'[PIC] Trouble with ICD2 + adaptor board (AC162050)'
2008\11\24@030333 by Artem Zezyulinskiy

flavicon
face
Hi!

Do you use a special ICD version of your PIC? (PIC12F675-ICD)

see header information on
http://ww1.microchip.com/downloads/en/DeviceDoc/51292h.pdf

Artem

2008\11\24@034626 by Alan B. Pearce

face picon face
>Do you use a special ICD version of your PIC? (PIC12F675-ICD)

Doesn't need the special header just to program it, only to debug it.

But it sounds to me like the ICD2 has popped its ICD driver devices, as they
are inclined to do.

I believe the routine is to raise a trouble ticket with Microchip, and they
exchange the ICD2 free of charge.

2008\11\24@043221 by Artem Zezyulinskiy

flavicon
face
Alan B. Pearce :
> Doesn't need the special header just to program it, only to debug it.
>  

Exact, but the OP said :

"ICD0083: Debug:  Unable to enter debug mode.  Please double click this
message for more information."

It's not debugging?

Or it's appear really during programming of PIC?


2008\11\24@121037 by Steve Smith

flavicon
face
Ok

Yes I am using a adaptor board (AC162050) and I don't think that there are
driver problems (it is working with a version of the same code on a F887) I
just had to finish off the section of code that was specific to the '675 and
the damm thing will only work the odd time... go back to the '887 its fine.

Steve

{Original Message removed}

2008\11\24@121059 by Steve Smith
flavicon
face
It wont enter debug after program...

Steve

-----Original Message-----
From: spam_OUTpiclist-bouncesTakeThisOuTspammit.edu [.....piclist-bouncesKILLspamspam@spam@mit.edu] On Behalf Of
Artem Zezyulinskiy
Sent: 24 November 2008 09:31
To: Microcontroller discussion list - Public.
Subject: Re: [PIC] Trouble with ICD2 + adaptor board (AC162050) for
Pic12f675

Alan B. Pearce :
> Doesn't need the special header just to program it, only to debug it.
>  

Exact, but the OP said :

"ICD0083: Debug:  Unable to enter debug mode.  Please double click this
message for more information."

It's not debugging?

Or it's appear really during programming of PIC?


2008\11\25@013727 by Artem Zezyulinskiy

flavicon
face
OK,

you can always send support ticket to microchip

Artem

Steve Smith a écrit :
> It wont enter debug after program...
>
> Steve
>  

2008\11\25@020402 by Xiaofan Chen

face picon face
On Mon, Nov 24, 2008 at 11:20 AM, Steve Smith <xygaxspamKILLspamblueyonder.co.uk> wrote:
>
> Guys :
>
> I have the following message when trying to program a 675 with known working
> code. The wdt and cp have been disabled and still this message..
>
> Any ideas... I have been through the help file and there is nothing obvious
>
> ..Validating configuration fields
> Connecting to debug executive
> Entering Debug Mode
> ...Programming GOTO 0x00 command
> ICD0083: Debug:  Unable to enter debug mode.  Please double click this
> message for more information.
> MPLAB ICD 2 ready for next operation

What is your configuration settings with 12F675? Since you are
using the ICD device (AC162050: PIC12F675-ICD), did you set
up the correct DIP switch? It is not easy to use ICD 2 with
12F675. Last time I was using 12F629 (with the same header)
and I had to give up to use the ICD 2 due to the fact I have
to use the internal MCLR and internal RC oscillator. In this
set up, ICD 2 is basically useless. I ended up using the
PICkit 1 as the programmer and oscilloscope as the
debugger.

Xiaofan

2008\11\25@170844 by Steve Smith

flavicon
face
I have just had one of those eureka moments... Not yet tried but planned

If the RC osc trim constant is overwritten each time you program it for
debug then its internal osc will be 'out' this may be the problem with it
not entering debug properly

Xiaofan...
Internal RC mclr internal boden off
2 pins are for comparator the rest is all digital. Signals are 700-2000us in
/ out on a 20mS time base. (radio control stuff)

J1 is on P1,2 as the destructions describe.

And the circuit is so simple ... servo in through comparator... servo out
and a led and an opto... so there is no loading on anything...

Thx Steve


{Original Message removed}

2008\11\25@183133 by Xiaofan Chen

face picon face
On Wed, Nov 26, 2008 at 6:08 AM, Steve Smith <.....xygaxKILLspamspam.....blueyonder.co.uk> wrote:
> I have just had one of those eureka moments... Not yet tried but planned
>
> If the RC osc trim constant is overwritten each time you program it for
> debug then its internal osc will be 'out' this may be the problem with it
> not entering debug properly
>

That is possible. You still need to check the help file for the limitation
with 12F675/12F629. Then you will find the limitation is so great
that ICD 2 is less useful for them.

For example, this is one of the limitations.
"Devices cannot be programmed or read while GP1/RA1 is high (Vih).
Move circuitry that makes GP1/RA1 high to another I/O pin during
development".

This is another one.
ICDWarn0033: You have selected Internal MCLR and Internal Oscillator
in your configuration settings. If your code makes use of port pins that
correspond to Clock and Data pins in programming mode, you may not
be able to reprogram your device. See on-line help for this warning for
more information. (OK/Cancel)


Xiaofan

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