Searching \ for '[PIC] MPLAB 8.6,PICKit 2,AC164110,AC162050:PK2' 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/languages.htm?key=mplab
Search entire site for: 'MPLAB 8.6,PICKit 2,AC164110,AC162050:PK2'.

No exact or substring matches. trying for part
PICList Thread
'[PIC] MPLAB 8.6,PICKit 2,AC164110,AC162050:PK2Erro'
2010\11\13@013328 by James Newton

face picon face
Trying to help a buddy out here. He has the latest version of MPLAB, an old
PICKit2, and he wants to develop some code in the 12F675. I told him he
really needs to be able to debug, and we looked up the docs for debugging
that chip with the PICKit2. As far as we can tell, you can do that with a
special header: The AC162050 which contains this special little version of
the chip: PIC12F675-ICD. To connect the AC162050 to the PICKit2, you must
have an ICSP to RJ-11 adapter, the AC164110. So we ordered both those parts
from Digikey and they arrived. We hook up the PICKit2, update the firmware,
connect the RJ11 adapter, and the AC162050. MPLAB sees the device, sees the
chip (once we got the RJ11 adapter on right way round) and we can program
code into it...

But we can't debug. It says:

PK2Error0028:  Unable to enter debug mode
NOTE: This device requires an ICD Header for debug.  See "Header
Specification" DS51292.
PICkit 2 Ready

http://ww1.microchip.com/downloads/en/DeviceDoc/51292S.pdf is exactly where
we found the info on which ICD header to purchase. And sure enough, it says
for the PIC12F675, you need an AC162050, which we have right here in front
of us, plugged into the PICKit2...

???

The jumper is in the right place (pins 1 and 2 are shorted) and we can
program the chip... and it verifies...
and won't debug...

help?

--
James Newton
1-970-462-7764

2010\11\13@054434 by Isaac Marino Bavaresco

flavicon
face
Em 13/11/2010 04:33, James Newton escreveu:
> Trying to help a buddy out here. He has the latest version of MPLAB, an old
> PICKit2, and he wants to develop some code in the 12F675. I told him he
> really needs to be able to debug, and we looked up the docs for debugging
> that chip with the PICKit2. As far as we can tell, you can do that with a
> special header: The AC162050 which contains this special little version of
> the chip: PIC12F675-ICD. To connect the AC162050 to the PICKit2, you must
> have an ICSP to RJ-11 adapter, the AC164110. So we ordered both those parts
> from Digikey and they arrived. We hook up the PICKit2, update the firmware,
> connect the RJ11 adapter, and the AC162050. MPLAB sees the device, sees the
> chip (once we got the RJ11 adapter on right way round) and we can program
> code into it...

Some of the first ICD header models have some special constraints (I
don't remember if some applies to 12F675):

1) Some devices won't work when using both internal oscillator and MCLR
disabled at same time.

2) Some devices won't work if a certain pin is pulled-up during reset (I
think it is RB4). This pin must be pulled low during reset. I think this
doesn't applies to 12F675.


Best regards,

Isaac

__________________________________________________
Fale com seus amigos  de graça com o novo Yahoo! Messenger http://br.messenger.yahoo.com

2010\11\13@061805 by Funny NYPD

picon face
This is a warning, when some of the configuration bits were not set up right, which will prevent the chip from entering the debugging mode. E.g. Debug bit wasn't turned on, WDT wasn't turned off, etc.

Funny N.
Au Group Electronics, http://www.AuElectronics.com
http://www.AuElectronics.com/products
http://augroups.blogspot.com/




________________________________
From: James Newton <spam_OUTjamesnewtonTakeThisOuTspammassmind.org>
To: Microcontroller discussion list - Public. <.....piclistKILLspamspam@spam@mit.edu>
Sent: Sat, November 13, 2010 1:33:25 AM
Subject: [PIC] MPLAB 8.6,PICKit 2,AC164110,AC162050:PK2Error0028

Trying to help a buddy out here. He has the latest version of MPLAB, an old
PICKit2, and he wants to develop some code in the 12F675. I told him he
really needs to be able to debug, and we looked up the docs for debugging
that chip with the PICKit2. As far as we can tell, you can do that with a
special header: The AC162050 which contains this special little version of
the chip: PIC12F675-ICD. To connect the AC162050 to the PICKit2, you must
have an ICSP to RJ-11 adapter, the AC164110. So we ordered both those parts
from Digikey and they arrived. We hook up the PICKit2, update the firmware,
connect the RJ11 adapter, and the AC162050. MPLAB sees the device, sees the
chip (once we got the RJ11 adapter on right way round) and we can program
code into it...

But we can't debug. It says:

PK2Error0028:  Unable to enter debug mode
NOTE: This device requires an ICD Header for debug.  See "Header
Specification" DS51292.
PICkit 2 Ready

http://ww1.microchip.com/downloads/en/DeviceDoc/51292S.pdf is exactly where
we found the info on which ICD header to purchase. And sure enough, it says
for the PIC12F675, you need an AC162050, which we have right here in front
of us, plugged into the PICKit2...

???

The jumper is in the right place (pins 1 and 2 are shorted) and we can
program the chip... and it verifies...
and won't debug...

help?

--
James Newton
1-970-462-7764

2010\11\13@084817 by Olin Lathrop

face picon face
James Newton wrote:
> Trying to help a buddy out here. He has the latest version of MPLAB,
> an old PICKit2, and he wants to develop some code in the 12F675. I
> told him he really needs to be able to debug, and we looked up the
> docs for debugging that chip with the PICKit2. As far as we can tell,
> you can do that with a special header: The AC162050 which contains
> this special little version of the chip: PIC12F675-ICD. To connect
> the AC162050 to the PICKit2, you must have an ICSP to RJ-11 adapter,
> the AC164110. So we ordered both those parts from Digikey and they
> arrived. We hook up the PICKit2, update the firmware, connect the
> RJ11 adapter, and the AC162050. MPLAB sees the device, sees the chip
> (once we got the RJ11 adapter on right way round) and we can program
> code into it...

I know you already got the hardware and want to make it work, but as a
alternative to just getting the code developed how about sticking to the
simulator?  I don't think I've ever used a ICE or other hardware debugger on
such a small chip.  The simulator is definitely the nicest debugging
environment if you can manage to simulate the inputs properly.  That
sometimes means writing host code to generate a .STI file, but that's
usually easy to do.


********************************************************************
Embed Inc, Littleton Massachusetts, http://www.embedinc.com/products
(978) 742-9014.  Gold level PIC consultants since 2000

2010\11\13@101314 by Herbert Graf

picon face
On Fri, 2010-11-12 at 22:33 -0800, James Newton wrote:
> But we can't debug. It says:
>
> PK2Error0028:  Unable to enter debug mode
> NOTE: This device requires an ICD Header for debug.  See "Header
> Specification" DS51292.
> PICkit 2 Ready

Have you selected the ICD part in MPLAB and not the "normal" part? Just
a guess.

TTYL

2010\11\13@105558 by Isaac Marino Bavaresco

flavicon
face
Em 13/11/2010 13:13, Herbert Graf escreveu:
> On Fri, 2010-11-12 at 22:33 -0800, James Newton wrote:
>> But we can't debug. It says:
>>
>> PK2Error0028:  Unable to enter debug mode
>> NOTE: This device requires an ICD Header for debug.  See "Header
>> Specification" DS51292.
>> PICkit 2 Ready
> Have you selected the ICD part in MPLAB and not the "normal" part? Just
> a guess.
>
> TTYL

There is no such a thing. When debugging a chip that needs a header,
MPLAB IDE expects the ICD version, but there is no special ICD version
on the list to select, just the normal one.

Isaac
..
__________________________________________________
Fale com seus amigos  de graça com o novo Yahoo! Messenger http://br.messenger.yahoo.com

2010\11\13@133525 by James Newton

face picon face
Thanks Isaac, tried it with RC and MCLR and RC w/o MCLR and no pins are
pulled anywhere.
--
James Newton
1-970-462-7764
{Original Message removed}

2010\11\13@134648 by James Newton

face picon face
I'm not finding a "debug bit" in the config.

The device selected is "PIC12F675" and that is the only option I see for
that device in the list. There is no debug version, as far as I can find,
e.g. no PIC12F675-ICD listed. The chip we are connected to IS a
PIC12F675-ICD.

The project build configuration is debug, not release

Under build options, on the compiler tab, Debug optimization is on.



Config is currently

FOSC    Oscillator Selection bits RC oscillator: I/O function on GP4/OSC2/CLKOUT pin, RC on GP5/OSC1/CLKIN

WDTE    Watchdog Timer Enable bit WDT disabled

PWRTE   Power-Up Timer Enable bit
PWRT disabled                                                      
MCLRE   GP3/MCLR pin function select
GP3/MCLR pin function is digital I/O, MCLR internally tied to VDD  
BOREN   Brown-out Detect Enable bit
BOD enabled                                                        
CP      Code Protection bit
Program Memory code protection is disabled                          
CPD     Data Code Protection bit
Data memory code protection is disabled  

Oh... hang on, there it was...

Should have been "INTOSC" not "RC oscillator" I was confusing that setting
for the /internal/ RC oscillator...

Ok, all better now... Thanks for the hint. PICList rocks as always!


--
James Newton
1-970-462-7764
{Original Message removed}

2010\11\13@181846 by Funny NYPD

picon face
>BOD enabled  
Try disable the brown out bit.


Funny N.
Au Group Electronics, http://www.AuElectronics.com
http://www.AuElectronics.com/products
http://augroups.blogspot.com/




________________________________
From: James Newton <jamesnewtonspamKILLspammassmind.org>
To: Microcontroller discussion list - Public. <.....piclistKILLspamspam.....mit.edu>
Sent: Sat, November 13, 2010 1:46:47 PM
Subject: RE: [PIC] MPLAB 8.6,PICKit 2,AC164110,AC162050:PK2Error0028

I'm not finding a "debug bit" in the config.

The device selected is "PIC12F675" and that is the only option I see for
that device in the list. There is no debug version, as far as I can find,
e.g. no PIC12F675-ICD listed. The chip we are connected to IS a
PIC12F675-ICD.

The project build configuration is debug, not release

Under build options, on the compiler tab, Debug optimization is on.



Config is currently

FOSC    Oscillator Selection bits RC oscillator: I/O function on GP4/OSC2/CLKOUT pin, RC on GP5/OSC1/CLKIN

WDTE    Watchdog Timer Enable bit WDT disabled

PWRTE   Power-Up Timer Enable bit
PWRT disabled                                                      
MCLRE   GP3/MCLR pin function select
GP3/MCLR pin function is digital I/O, MCLR internally tied to VDD  
BOREN   Brown-out Detect Enable bit
BOD enabled                                                        
CP      Code Protection bit
Program Memory code protection is disabled                          
CPD     Data Code Protection bit
Data memory code protection is disabled  

Oh... hang on, there it was...

Should have been "INTOSC" not "RC oscillator" I was confusing that setting
for the /internal/ RC oscillator...

Ok, all better now... Thanks for the hint. PICList rocks as always!


--
James Newton
1-970-462-7764
{Original Message removed}

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