Bah, Humbug!! Microchip has pulled a fast one on us who prefer not to use MPLAB.
Got bit by the Debug bit for a 18LF1422, just like . Solution: Plug GCBasic assembler into MPLAB, then make the project in release mode, and program from the MPLAB IDE, Not fun in my book.
Would be nice, perhaps necessary, to turn the Debug bit off at GCBasic compile time. Just not sure at the moment where the invisible Debug bit is.
Hopefully the invisible DEBUG config bit is in the same place as the visible config bit on most other 18F chips. I've added a definition for the DEBUG bit to the chip data file for the 18F/LF14K22 in <a>http://gcbasic.sourceforge.net/newfiles/update.zip</a>, so GCBASIC's built in assembler should now automatically clear it.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks Hugh for the update. Still having problems. Tried compiling with default GCASM and MPASM, and the config word still compare the same. Normally use MPASM. Hope this is not a PICKIT 2 programming issue?
;Program compiled by Great Cow BASIC (0.9 15/11/2009)
;Need help? See the GCBASIC forums at http://sourceforge.net/forum/?group_id=169286,
;check the documentation or email w_cholmondeley@users.sourceforge.net.
Arrrrghhh, of course it works. Sometimes it pays to take a break. Was trying to make GCASM work from MAKEASM.BAT rather than the proper COMPILE.BAT using /A:GCASM…..doh!
GCASM doesn't appear to like the Debug bit definition (just like MPASM), not that it matters, as it works perfectly without it.
Bah, Humbug!! Microchip has pulled a fast one on us who prefer not to use MPLAB.
Got bit by the Debug bit for a 18LF1422, just like . Solution: Plug GCBasic assembler into MPLAB, then make the project in release mode, and program from the MPLAB IDE, Not fun in my book.
Would be nice, perhaps necessary, to turn the Debug bit off at GCBasic compile time. Just not sure at the moment where the invisible Debug bit is.
Kent
: http://www.piclist.com/techref/postbot.asp?by=thread&id=+PIC18LF1xKxx+-+I+want+my+DEBUG+bit!&w=body&tgt=_top
Hopefully the invisible DEBUG config bit is in the same place as the visible config bit on most other 18F chips. I've added a definition for the DEBUG bit to the chip data file for the 18F/LF14K22 in <a>http://gcbasic.sourceforge.net/newfiles/update.zip</a>, so GCBASIC's built in assembler should now automatically clear it.
Thanks Hugh for the update. Still having problems. Tried compiling with default GCASM and MPASM, and the config word still compare the same. Normally use MPASM. Hope this is not a PICKIT 2 programming issue?
;Program compiled by Great Cow BASIC (0.9 15/11/2009)
;Need help? See the GCBASIC forums at http://sourceforge.net/forum/?group_id=169286,
;check the documentation or email w_cholmondeley@users.sourceforge.net.
;********************************************************************************
;Set up the assembler options (Chip type, clock source, other bits and pieces)
LIST p=18LF14K22, r=DEC
#include <P18LF14K22.inc>
CONFIG LVP = OFF, MCLRE = OFF, WDTEN = OFF, PLLEN = OFF, FOSC = IRC
;********************************************************************************
And the config word as reported by PICKIT 2 for both assemblers.
2800 1E1F 0800 0001
C003 E003 4003
As stated from the Microchip support/Piclist link, the config word needs to be set in hex now for these devices?
Should mention that tried #Config Debug = Off with GCASM too, and still no go.
Arrrrghhh, of course it works. Sometimes it pays to take a break. Was trying to make GCASM work from MAKEASM.BAT rather than the proper COMPILE.BAT using /A:GCASM…..doh!
GCASM doesn't appear to like the Debug bit definition (just like MPASM), not that it matters, as it works perfectly without it.
------- Capture Output -------
"C:\Program Files\GCBasic\Compile.bat" C:\PROGRA~1\CRIMSO~3\18FXXX~1\18LF14~1
Great Cow BASIC (0.9 12/8/2009)
Compiling C:\PROGRA~1\CRIMSO~3\18FXXX~1\18LF14~1 …
Done
Assembling program …
An error has been found:
Error: GCASM: Configuration setting not valid: DEBUG = OFF
The message has been logged to the file Errors.txt.
Press any key to continue