16f88 configuration ..... and pickit2 configuration word warning....

@ DEVICE PIC16F88, INTRC_OSC_NOCLKOUT
@ DEVICE PIC16F88, WRT_OFF
@ DEVICE PIC16F88, DEBUG_OFF
@ DEVICE PIC16F88, CCPMX_OFF
@ DEVICE PIC16F88, MCLR_OFF
@ DEVICE PIC16F88, PROTECT_OFF
@ DEVICE PIC16F88, CPD_OFF
@ DEVICE PIC16F88, LVP_OFF
@ DEVICE PIC16F88, BOD_OFF
@ DEVICE PIC16F88, PWRT_OFF
@ DEVICE PIC16F88, WDT_OFF
@ DEVICE PIC16F88, CCPMX_OFF

@ DEVICE2 PIC16F88, FCMEN_OFF
@ DEVICE2 PIC16F88, IESO_OFF


Here it is... DEVICE2 is not recognized (illegal device type).

If i use DEVICE instead of DEVICE2 , it compiles normally , but the PICKIT2 says ' some configuration bits are not set...'
(not using MPASM of course)

And even if i ignore the warning , at the end , i get Error Verification in configuration word........

Thanks in advance!!!

Depends what version of PBP you have. If my crystal ball is working correctly, this might be the right answer http://www.picbasic.co.uk/forum/showthread.php?t=13724

with an added line for

@ __CONFIG _CONFIG2, _IESO_OFF & _FCMEN_OFF

unfortunately as i said i don't use MPASM ....

(PBP 2.60C)

I think with PM, you can just use the @ DEVICE, and don't need to specify @DEVICE2 (especially since @ DEVICE PIC16F88, INTRC_OSC_NOCLKOUT is really defining config1 configs). I would use your @ DEVICE on all the configs you wish to set. However, I don't use PM, so I could be wrong about this. The warning about all configs not being set, is just a warning. There are a few more configs that are not set. Here is the complete list for the 16F88.

EDIT:

It looks like you do name all the configs, so I don't know why you are getting a warning. Although, you do name CCPMX twice .., shouldn't matter though.

Thanks for the interest but all these are for MPASM.... i am not sure if i can handle MPASM.... if until tommorow morning have no reply i will try using MPASM.

Quote:

---

but the PICKIT2 says ' some configuration bits are not set...'

---

All the PicKit2 software is telling you is there are more things that can be set in the configs. Being that you are happy with leaving the remainder to their default setting just ignore the warning.

Quote:

---

@ DEVICE2 PIC16F88, FCMEN_OFF
@ DEVICE2 PIC16F88, IESO_OFF

---

The above is not needed in your case as you are using the internal OSC. Not sure why PM is causing the error, but you should be fine by not including the two lines.

Quote:

---

Originally Posted by LakisFM1

@ DEVICE PIC16F88, INTRC_OSC_NOCLKOUT
@ DEVICE PIC16F88, WRT_OFF
@ DEVICE PIC16F88, DEBUG_OFF
@ DEVICE PIC16F88, CCPMX_OFF
@ DEVICE PIC16F88, MCLR_OFF
@ DEVICE PIC16F88, PROTECT_OFF
@ DEVICE PIC16F88, CPD_OFF
@ DEVICE PIC16F88, LVP_OFF
@ DEVICE PIC16F88, BOD_OFF
@ DEVICE PIC16F88, PWRT_OFF
@ DEVICE PIC16F88, WDT_OFF
@ DEVICE PIC16F88, CCPMX_OFF

@ DEVICE2 PIC16F88, FCMEN_OFF
@ DEVICE2 PIC16F88, IESO_OFF


Here it is... DEVICE2 is not recognized (illegal device type).

---

Do them like this ...

Code:

---

@ DEVICE PIC16F88, INTRC_OSC_NOCLKOUT
 @ DEVICE WRT_OFF
 @ DEVICE DEBUG_OFF
 @ DEVICE CCPMX_OFF
 @ DEVICE MCLR_OFF
 @ DEVICE PROTECT_OFF
 @ DEVICE CPD_OFF
 @ DEVICE LVP_OFF
 @ DEVICE BOD_OFF
 @ DEVICE PWRT_OFF
 @ DEVICE WDT_OFF
 @ DEVICE CCPMX_OFF
 '
 @ DEVICE2 FCMEN_OFF
 @ DEVICE2 IESO_OFF

---

The PIC part number is not required, and certainly not in every DEVICE line.
One instance can be handy, as it will cause an error if you compile the program for the wrong chip.

DEVICE2 doesn't like the part number at all.