PICKit2 - warning about configuration words

[Acetronics2]

Hi, Roger

With MPASM used ... you're to use MPASM syntax !
With PM used ... you're to use PM syntax !

That written ...

MPASM .INC files give you ALL the settings available ... in the MPASM syntax, of course !!!

... capito ???

and, first of all CCPMX_OFF doesn't exist ... you've to CHOOSE your output Pin ...

yes ... D.A.T.A.S.H.E.E.T. !!!

Dur, dur ...

Alain

[flotulopex]

MPASM .INC files give you ALL the settings available ... in the MPASM syntax, of course !!! ... capito ???

¡Si Señor! I think I know that. So where can I find the correct syntax for MCS then??? Me parece qué esto es más difícil.

first of all CCPMX_OFF doesn't exist ... you've to CHOOSE your output Pin..

Hereunder, I highlighted the parameters I replaced by the ones I use normally (in comment) and see what happens (error msg) when the program is compiled by MCS.

Ah?
<img src="http://www.picbasic.co.uk/forum/attachment.php?attachmentid=2753&stc=1&d=121639034 1">
Oh!
<img src="http://www.picbasic.co.uk/forum/attachment.php?attachmentid=2754&stc=1&d=121639034 1">
Hmmmm...
<img src="http://www.picbasic.co.uk/forum/attachment.php?attachmentid=2755&stc=1&d=121639034 1">
As you can see, some "original" syntax from the MicroChip file won't be accepted in MCS. I understand MCS is not using "as is" all or part of the content of .INC files. Am I really wrong?

[skimask]

So where can I find the correct syntax for MCS then???

It's not so much the correct syntax for MCS, it's more the correct syntax for the compiler/assembler you are using.
If it's MPASM, the config registers are listed in that particular MCUs INC file in the MPASM directory near the end of the file (usually).
If it's PM, their listed in that particular MCUs INC file in the PBP INC directory near the beginning of the file (usually).

[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>