Make a "Complete" set of configs for any chip with ease.
meCONFIG
http://support.melabs.com/content/563-meCONFIG
Make a "Complete" set of configs for any chip with ease.
meCONFIG
http://support.melabs.com/content/563-meCONFIG
DT
Yes the pickit 2 software states when programming that some configuration bits not in acceptable condition. It still programs and works fine but is disconcerting for users.
That new meconfig software is interesting I see quite a few bits/parameters I have ignored/did not know about. :?
Last edited by retepsnikrep; - 11th March 2014 at 18:00.
The PICkit software expects to see a value for EVERY configuration word.
The latest versions of PBP3 do create default values for all of them.
But when you use the #CONFIG block, it overrides all of the defaults, and you should include a "Complete" set for use with the PICkit programmers.
Like you said, it will program and work ... but a complete set of configs will eliminate that warning.
DT
melabs have a neat config editor meCONFIG ITS WORTH DOWNLOADING and free , or check out the DEVICE_REFERENCE folder in your pbp3 installed directory
but for now try this
Code:#CONFIG CONFIG OSC = INTIO67 CONFIG FCMEN = OFF CONFIG IESO = OFF CONFIG PWRT = OFF CONFIG BOREN = OFF CONFIG BORV = 3 CONFIG WDT = ON CONFIG WDTPS = 512 CONFIG CCP2MX = PORTC CONFIG PBADEN = OFF CONFIG LPT1OSC = OFF CONFIG MCLRE = ON CONFIG STVREN = ON CONFIG LVP = OFF CONFIG XINST = OFF CONFIG DEBUG = OFF CONFIG CP0 = OFF CONFIG CP1 = OFF CONFIG CP2 = OFF CONFIG CP3 = OFF CONFIG CPB = OFF CONFIG CPD = OFF CONFIG WRT0 = OFF CONFIG WRT1 = OFF CONFIG WRT2 = OFF CONFIG WRT3 = OFF CONFIG WRTC = OFF CONFIG WRTB = OFF CONFIG WRTD = OFF CONFIG EBTR0 = OFF CONFIG EBTR1 = OFF CONFIG EBTR2 = OFF CONFIG EBTR3 = OFF CONFIG EBTRB = OFF #ENDCONFIG
ps not sure why your asking for PIC18F4520 config info in a 18F2620 thread why not start a new one ?
Last edited by richard; - 26th November 2014 at 00:17.
the correct syntax and available config word (fuse) settings are available in the pbp3 device_reference folder
File: PIC18F4520.INFO
Code:;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; Available configuration settings for PIC18F4520: ; ; ; Oscillator Selection bits ; CONFIG OSC = INTIO7 ;Internal oscillator block, CLKO function on RA6, port function on RA7 ; CONFIG OSC = INTIO67 ;Internal oscillator block, port function on RA6 and RA7 ; CONFIG OSC = RCIO6 ;External RC oscillator, port function on RA6 ; CONFIG OSC = HSPLL ;HS oscillator, PLL enabled (Clock Frequency = 4 x FOSC1) ; CONFIG OSC = ECIO6 ;EC oscillator, port function on RA6 ; CONFIG OSC = EC ;EC oscillator, CLKO function on RA6 ; CONFIG OSC = RC ;External RC oscillator, CLKO function on RA6 ; CONFIG OSC = HS ;HS oscillator ; CONFIG OSC = XT ;XT oscillator ; CONFIG OSC = LP ;LP oscillator
Assembler uses columns, leave the same spacing as in the INC file.
Robert
according to the book if I have the right code
if that doesn't help you might need to post your latest code217 Attempt to Generate Code in Non-Code Segment
Due to the Harvard Architecture (split code and data spaces) of the PICmicro
MCUs, instructions may only be executed from CODE space (ROM). This error
indicates that an attempt was made to generate opcodes in the data or
EEPROM segments. In general, only the DS pseudo-op is legal in the data
segment and DS, DB and DW are the only legal pseudo-ops in the EEPROM
segment.
Bookmarks