gnupic: Re: [gnupic] gpasm - __CONFIG
Subject:
RE: [gnupic] gpasm - __CONFIG
From:
"Chen Xiao Fan" ####@####.####
Date:
12 Jan 2006 08:20:38 +0000
Message-Id: <7D4AB72251D4D949AB2732ABEABDA54F12FFAF@PFSG-MX1.ap.p-f.biz>
> -----Original Message-----
> From: Scott Dattalo ####@####.####
> Sent: Tuesday, November 01, 2005 1:02 AM
> To: ####@####.####
> Subject: Re: [gnupic] gpasm - __CONFIG
> Chen Xiao Fan wrote:
>> It is not a bug of gpasm per se. Microchip MPASM will fail as well
>> but it will issue an error. The use of "__config" for PIC18 is now
>> deprecated for MPASM. It is better to use "config" instead.
>
> Hi Xiaofan,
>
> Thanks for pointing this out. I verified that gpasm does not
> support the "config" directive. I also filed a bug report.
> Meanwhile, I'll continue to use the __config directive and
> just make sure that the order is correct.
>
> Scott
Any updates on this? Starting from MPASM 4.02 (comes with
MPLAB 7.22, released 17 July 2005), __CONFIG does not
support the PIC18J device and this __CONFIG is really
deprecated for MPASM. I guess they will obsolete it
slowly when they introduce new PIC18F device. Maybe it
is a good idea to support CONFIG under gpasm.
From the release notes of MPASM(TM) 4.02:
"Starting with this release, the __CONFIG directive is not supported
for PIC18 J Flash devices. An error will be given if the __CONFIG
directive is used. Use the CONFIG directive instead.
The __CONFIG directive has been deprecated for all other PIC18
devices. A warning will be issued if the __CONFIG directive is used
with one of these devices."
Regards,
Xiaofan
