gnupic: gpasm - __CONFIG
Subject:
gpasm - __CONFIG
From:
"Scott Dattalo" ####@####.####
Date:
31 Oct 2005 04:18:37 +0000
Message-Id: <60418.71.139.60.68.1130732313.squirrel@71.139.60.68>
Does anyone know if the order is supposed to matter for __CONFIG
directives in 18F devices? In absolute mode, gpasm doesn't care about the
order of the __CONFIG directives. However in relocatable mode it does.
For example,
__CONFIG _CONFIG1H, _HSPLL_OSC_1H & _OSCS_ON_1H
__CONFIG _CONFIG2H, _WDT_ON_2H
__CONFIG _CONFIG4L, _LVP_OFF_4L
__CONFIG _CONFIG5L, _CP0_ON_5L & _CP1_ON_5L
__CONFIG _CONFIG5H, _CPB_ON_5H
generates this in the hex file:
:0E000000FFDEFFFFFFFFFBFFFCBFFFFFFFFF68
Where as:
__CONFIG _CONFIG2H, _WDT_ON_2H
__CONFIG _CONFIG1H, _HSPLL_OSC_1H & _OSCS_ON_1H
__CONFIG _CONFIG4L, _LVP_OFF_4L
__CONFIG _CONFIG5L, _CP0_ON_5L & _CP1_ON_5L
__CONFIG _CONFIG5H, _CPB_ON_5H
generates:
:0C000200FFFFFFFFFBFFFCBFFFFFFFFF45
In Absolute mode, the latter example generates:
:04000000FFDEFFFF21
:04000600FBFFFCBF41
----
Does MPASM behave the same way? Is this a bug in gpasm?
Scott
