gnupic: Re: [gnupic] Re: [PATCH] CONFIG feature progress
Subject:
RE: [gnupic] Re: [PATCH] CONFIG feature progress
From:
"Chen Xiao Fan" ####@####.####
Date:
20 Jan 2006 07:26:29 +0000
Message-Id: <7D4AB72251D4D949AB2732ABEABDA54F12FFD8@PFSG-MX1.ap.p-f.biz>
> From: Michael Ballbach
> Sent: Friday, January 20, 2006 3:35 AM
>
> I've posted a proof-of-concept level patch at:
>
> http://wayreth.rten.net/~ballbach/gputils/
>
> to support PIC18 style CONFIG directives. Works for my
> project with the 18F2455, but I've not tested it extensively. Notes:
>
> 1) Since defaults for a device are known, I fill the section with
> defaults, instead of 0xff. If CONFIG is never used in the module, no
> defaults are filled in. That is, using __CONFIG should not change any
> behavior. The only time defaults are added is when CONFIG is seen for
> the first time.
>
> 2) Instead of using 0xff where there are holes in the section, I use
> 0x00, since a device burned with MPLAB seems to read 0x00 in
> the holes during a table read. This is instead of just omitting
> them altogether from the HEX file, since this is somewhat difficult
> to do.
>
> 3) As in MPASM, using __CONFIG and CONFIG together generates
> an error.
>
I just tried the patch on the gputils snapshot version dated
19-Dec-2005. Now the CONFIG directive is kind of working.
I am using an simple example from MPLAB template 2550temp.asm.
The interesting line is the following:
; Oscillator Selection:
CONFIG FOSC = XT_XT ;XT oscillator, XT used by USB
MPASMWIN 5.0 generates the following for the above line:
:020000040030CA
:040000002F000F1F9F
:020005008085F4
:060008000FC00FE00F40E5
Patched gpasm generated the following (unpatched
version will fail with CONFIG directive):
:020000040030CA
:020000002F00CF
Somewhat the default values and the 00 filled bytes are
not inside the hex file with the current patch. Maybe there
is something wrong with the patch but I am testing this
under Windows. I will test it under Linux as well.
Regards,
Xiaofan
