Hi, for me this well working for 18F258 and MPLAB 6.13  :

 __CONFIG    _CONFIG1L, _CP_OFF_1L
 __CONFIG    _CONFIG1H, _OSCS_OFF_1H & _XT_OSC_1H
 __CONFIG    _CONFIG2L, _BOR_ON_2L & _BORV_27_2L & _PWRT_ON_2L
 __CONFIG    _CONFIG2H, _WDT_ON_2H & _WDTPS_128_2H
; __CONFIG    _CONFIG3L,
; __CONFIG    _CONFIG3H,
 __CONFIG    _CONFIG4L, _STVR_ON_4L & _DEBUG_OFF_4L & _LVP_OFF_4L
; __CONFIG    _CONFIG4H,
 __CONFIG    _CONFIG5L, 0xff
 __CONFIG    _CONFIG5H, 0xff
 __CONFIG    _CONFIG6L, 0xff
 __CONFIG    _CONFIG6H, 0xff
 __CONFIG    _CONFIG7L, 0xff
 __CONFIG    _CONFIG7H, 0xff

 __IDLOCS    _IDLOC0, <expression>
 __IDLOCS    _IDLOC1, <expression>
 __IDLOCS    _IDLOC2, <expression>
 __IDLOCS    _IDLOC3, <expression>
 __IDLOCS    _IDLOC4, <expression>
 __IDLOCS    _IDLOC5, <expression>
 __IDLOCS    _IDLOC6, <expression>
 __IDLOCS    _IDLOC7, <expression>


Regard,
david.vyskocil@wanadoo.fr


> Hi all,
>
> There seems to be some discrepancies with FUSES in these chips.
>
> The programming spec lists up to 7 words for FUSE locations, but also
> mentions only 4 FUSE words used. 4 words are listed in the 18F252.INC
> file, 7 listed in 18F258.INC.
>
> MPLAB seems to keep all 7 words shown in it's programming window, and
> only varies the CCP2 Mux between chips which is also listed in the data
> sheet as being correct.
>
> You also get compile errors if you try to code protect sections of ROM
> because they are not included in the INC files.
>
>
> Is any of this correct ???  :-)

--
http://www.piclist.com hint: To leave the PICList
mailto:piclist-unsubscribe-request@mitvma.mit.edu