PICKit2 - warning about configuration words

[bcd]

OK - first things first.

Are you compiling with MPASM or the PM assembler ? A look at the Compile and Program Options from the View menu in MCS.

Here is an example of a config line from a project that uses MPASM:
@ __CONFIG _CONFIG1H, _IESO_OFF_1H & _FCMEN_OFF_1H & _OSC_INTIO2_1H

I have also founds that the PicKit2 will complain about this if you do not define every single CONFIG register. I normally define what I know I need to set and leave the rest. It burns and runs fine.

there are a series of defaults in the .INC file in the PBP folder for each chip.

For the 16F87 it looks like :
<code>
;************************************************* ***************
;* 16F87.INC *
;* *
;* By : Leonard Zerman, Jeff Schmoyer *
;* Notice : Copyright (c) 2004 microEngineering Labs, Inc. *
;* All Rights Reserved *
;* Date : 01/07/04 *
;* Version : 2.45 *
;* Notes : *
;************************************************* ***************
NOLIST
ifdef PM_USED
LIST
include 'M16F87.INC' ; PM header
*** device pic16F87, hs_osc, wdt_on, lvp_off, protect_off
XALL
NOLIST
else
LIST
LIST p = 16F87, r = dec, w = -302
INCLUDE "P16F87.INC" ; MPASM Header
*** __config _CONFIG1, _HS_OSC & _WDT_ON & _LVP_OFF & _CP_OFF
NOLIST
endif
LIST

</code>

It have put *** to hi light the default the compiler will insert. Using PM the program will use the ones you specify in your code rather than the ones in the INC file. Using MPASM you will get warning about over-writing the contents of the CONFIG bits.

When I moved to MPASM I had to spent a bit of time working out what things were called as some of the names changed. Check out the MPASM INC files to workout what things are called.


bill

EDIT: Looking at you original post you are using PM. Just ignore the warnings - its just the PicKit2 being anal about making sure everything is defined.

[flotulopex]

I use PM.

Thanks for this clarification.

PICkit2 is really great and I was just wondering about those warning I don't get with other PICs.

[botsmaker]

I too sometimes have a problem with pickit2 recognizing the 16f88. It will state that the device is unsupported. It always has a problem with the hex file not having a complete configuration. I gave up using the 16F88 with pickit2.

[Darrel Taylor]

The missing CONFIG words are because the 16F88 has two CONFIG words.

When using PM, DEVICE sets CONFIG1 and DEVICE2 sets CONFIG2.

@ DEVICE  HS_OSC, WDT_OFF, PWRT_ON ; etc
@ DEVICE2 FCMEN_OFF, IESO_OFF

I too sometimes have a problem with pickit2 recognizing the 16f88. It will state that the device is unsupported.

Hmmm, that's odd.
No idea for that one.
<br>

[Dave]

botsmaker, and others... Have any of you out there updated the OS for the pickit2? I havent had any problems with it programming 16F88 or any other pic's...

Dave Purola,
N8NTA

[botsmaker]

Just updated application software to 2.61 and updated OS to 2.32. I get the same response. It will recon the device when I connect it, then when I load the hex file I get the warning. "Device Error-hex file not loaded", "Unsupported part". I'm using micro studio and PBP.

[botsmaker]

This is the warning message I get from pickit2

[flotulopex]

DEVICE sets CONFIG1 and DEVICE2 sets CONFIG2.

Darrel,

Where a hell did you find this information? Come on, tell us, you're working for the NSA or ex-KGB people, no?

Anyway, thanks a lot!!!

[Bruce]

Where a hell did you find this information?

It's explained in the PM assembler manual. PM.TXT.

[Darrel Taylor]

Bruce knew where it was...

Come on, tell us, you're working for the NSA or ex-KGB people, no?

I'd tell you, but then I'd have to kill you.
<br>

[flotulopex]

Brrrrr!!!

Some freezing sweat drops fall along my back. Okay then, I better never ever ask this question again

NB: just a shame this info was not in some help file (MCS or PBP); would have been easier to find for me.