Searching \ for '[PIC]: PIC18F6520 Unable to put it in debug mode' 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/devices.htm?key=18F
Search entire site for: 'PIC18F6520 Unable to put it in debug mode'.

Exact match. Not showing close matches.
PICList Thread
'[PIC]: PIC18F6520 Unable to put it in debug mode'
2009\04\03@155026 by Andre

flavicon
face
Hi to all,

I am using 18f6520 and I am unable to put it in debug mode but I can program ok.
There is no resistor or capacitor sitting on data or clock like all clear.
I am able to use pic18f4550 in debug mode and it works fine but not pic18f6520.
I also tried REAL ICE same thing. I looks like some thing is different on this chip.
on configuration fuses I have WDT off and DEBUG enable.
I use CCS v 4.84 and here is the config fuses.
I do not remember what error massage was but as soon as I get home I can find out.

#FUSES NOWDT //Watch Dog Timer
#FUSES WDT128 //Watch Dog Timer uses 1:128 Postscale
#FUSES EC_IO //External clock
#FUSES NOPROTECT //Code not protected from reading
#FUSES NOOSCSEN //Oscillator switching is disabled, main oscillator is source
#FUSES BROWNOUT //Reset when brownout detected
#FUSES BORV42 //Brownout reset at 4.2V
#FUSES PUT //Power Up Timer
#FUSES NOCPD //No EE protection
#FUSES STVREN //Stack full/underflow will cause reset
#FUSES DEBUG //Debug mode for use with ICD
#FUSES NOLVP //NO Low Voltage Programming on B3(PIC16) or B5(PIC18)
#FUSES NOWRT //Program memory not write protected
#FUSES NOWRTD //Data EEPROM not write protected
#FUSES NOEBTR //Memory not protected from table reads
#FUSES NOCPB //No Boot Block code protection
#FUSES NOEBTRB //Boot block not protected from table reads
#FUSES NOWRTC //configuration not registers write protected
#FUSES NOWRTB //Boot block not write protected
#FUSES CCP2E7 //CCP2 input/output multiplexed with RE7

At this moment I use mplab and ICD2 to program


any help will appreciate

thank you

Andre
       

2009\04\03@164039 by davidcou

picon face
Try turning off the POWER UP TIMER in the Config Register during DEBUG.

There are known limitations on some parts in this family that do NOT allow DEBUG when BROWNOUT RESET along with POWER ON TIMER are enabled in the config register.

But, remember to turn the POWER ON TIMER back on before running out of debug.

I hope this helps.

David


{Original Message removed}

2009\04\03@164102 by Barry Gershenfeld

picon face
>
> I am using 18f6520 and I am unable to put it in debug mode but I can
> program ok.
> There is no resistor or capacitor sitting on data or clock like all clear.
> I am able to use pic18f4550 in debug mode and it works fine but not
> pic18f6520.
> I also tried REAL ICE same thing. I looks like some thing is different on
> this chip.
> on configuration fuses I have WDT off and DEBUG enable.
> I use CCS v 4.84 and here is the config fuses.
> I do not remember what error massage was but as soon as I get home I can
> find out.
>
> #FUSES EC_IO //External clock
> #FUSES DEBUG //Debug mode for use with ICD
>

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

The causes are many, and that link has 10 suggestions to check (most are
eliminated by the fact that it works on your 4550).  Some more that have
worked for me:

- Disable port B pullups.  Don't know why, but try it.
- Shorter programming cable.  Make one as short as practical and try it any
time this problem happens, before you look deeper for other causes.
- Reset line not controllable.  I had a board with an external watchdog chip
and it drove me crazy...impossible to debug without disabling it.

I noted that chip is only rated to 25 MHz with EC_IO.  Faster clocks give me
more problems (incidentally, the 4550 was on of those).

Many people run into this problem.  Try some things and report back to us.

Barry

2009\04\03@171349 by Andre

flavicon
face

David,

I am at work right now but I just checked the code both of them are on.
I will try it as soon as I get home.

thanks

Andre


--- spam_OUTdavidcouTakeThisOuTspamaol.com wrote:

From: .....davidcouKILLspamspam@spam@aol.com
To: piclistspamKILLspammit.edu
Subject: Re: [PIC]: PIC18F6520 Unable to put it in debug mode
Date: Fri, 03 Apr 2009 16:40:22 -0400

Try turning off the POWER UP TIMER in the Config Register during DEBUG.

There are known limitations on some parts in this family that do NOT allow DEBUG when BROWNOUT RESET along with POWER ON TIMER are enabled in the config register.

But, remember to turn the POWER ON TIMER back on before running out of debug.

I hope this helps.

David


{Original Message removed}

2009\04\03@171525 by Andre
flavicon
face

Barry,

very good I will try and let you guys know.

thank you very much

Andre


--- .....gbarry42KILLspamspam.....gmail.com wrote:

From: Barry Gershenfeld <EraseMEgbarry42spam_OUTspamTakeThisOuTgmail.com>
To: "Microcontroller discussion list - Public." <piclistspamspam_OUTmit.edu>
Subject: Re: [PIC]: PIC18F6520 Unable to put it in debug mode
Date: Fri, 3 Apr 2009 13:41:01 -0700

{Quote hidden}

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

The causes are many, and that link has 10 suggestions to check (most are
eliminated by the fact that it works on your 4550).  Some more that have
worked for me:

- Disable port B pullups.  Don't know why, but try it.
- Shorter programming cable.  Make one as short as practical and try it any
time this problem happens, before you look deeper for other causes.
- Reset line not controllable.  I had a board with an external watchdog chip
and it drove me crazy...impossible to debug without disabling it.

I noted that chip is only rated to 25 MHz with EC_IO.  Faster clocks give me
more problems (incidentally, the 4550 was on of those).

Many people run into this problem.  Try some things and report back to us.

Barry

2009\04\24@180342 by Bob Axtell

face picon face
While many will snicker, trust me on this: only MPLAB 7.4 and 7.6 work
properly on
the ICD2. Every other version of MPLAB hangs and locks up constantly,
and "can't enter debug mode" is one of the symptoms. MPLAB7.4 works so
good I can go home over the weekend, come in, password-enable my PC,
and can immediately start where I left off
on Friday.

Try  it.

-- Bob

On Fri, Apr 3, 2009 at 2:15 PM,  <@spam@andreKILLspamspamditechnology.com> wrote:
{Quote hidden}

>

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