gnupic: Thread: gpasm extended mode -- MPLAB message


[<<] [<] Page 1 of 1 [>] [>>]
Subject: gpasm extended mode -- MPLAB message
From: Sivaram Gowkanapalli ####@####.####
Date: 3 Jun 2011 05:14:02 -0000
Message-Id: <SNT125-W5796AB299AE71BEB29A9D5D27F0@phx.gbl>

Hello,

I built the below file with gpasm and gplink. 

But, when I import the test.cof file into MPLAB, MPLAB
complains with a message of "The Extended CPU Mode Configuration
bit is enabled, but the program that was loaded was not built using extended 
CPU instructions. Therefore, your code may not work properly"

I used the --extended flag with gpasm and alos used the latest svn version 
of gpasm. Just wanted to check if the extended mode of gpasm actually works.

; ============ test.asm begin
; Build commands
; gpasm --extended --object test.asm

; gplink --map --object --output test.hex test.o
;message: using default linker script "/usr/local/share/gputils/lkr/18f4455.lkr"

   errorlevel 0
   list p=18f4455 ; set processor type
   list n=0 ; supress page breaks in list file
   include <p18f4455.inc>
   include <coff.inc>
   ; Instruction set extension and Indexed Addressing mode enabledd
   CONFIG XINST   = ON

vars udata 0x00
_temp res 1

RESET_VECTOR CODE 00000h ; Reset and Interrupt Vectors
   pagesel start
   goto start
MAIN CODE
   global start
start

   lfsr 2, 0xff
   movlw 0xff
   ;movff WREG,_temp
   movwf _temp,ACCESS
   incf _temp,F,ACCESS
   incf _temp,F,ACCESS
   incf _temp,F,ACCESS
   pushl 0x1

end
;============== test.asm end

Thanks
Siva
 		 	   		  
Subject: Re: gpasm extended mode -- MPLAB message
From: Marko Kohtala ####@####.####
Date: 3 Jun 2011 05:54:10 -0000
Message-Id: <BANLkTi=RSEFLtDOk8_gUtyWR9A=nMj+utg@mail.gmail.com>

No. Comparing the COFF help file from MPASM 5.40 against gpcoff.h,
flags F_ABSOLUTE and F_EXTENDED18 seem to be missing from the COFF
file headers. Maybe Microchip has added them at some point but gputils
has not been updated. These changes in COFF may be part of the changes
Microchip did while they stopped using COD files.

I think you should add this to the tracker at sourceforge. If not a
patch with test cases, a bug report at least.

Marko

On Fri, Jun 3, 2011 at 8:14 AM, Sivaram Gowkanapalli
####@####.#### wrote:
>
> Hello,
>
> I built the below file with gpasm and gplink.
>
> But, when I import the test.cof file into MPLAB, MPLAB
> complains with a message of "The Extended CPU Mode Configuration
> bit is enabled, but the program that was loaded was not built using extended
> CPU instructions. Therefore, your code may not work properly"
>
> I used the --extended flag with gpasm and alos used the latest svn version
> of gpasm. Just wanted to check if the extended mode of gpasm actually works.
>
> ; ============ test.asm begin
> ; Build commands
> ; gpasm --extended --object test.asm
>
> ; gplink --map --object --output test.hex test.o
> ;message: using default linker script "/usr/local/share/gputils/lkr/18f4455.lkr"
>
>   errorlevel 0
>   list p=18f4455 ; set processor type
>   list n=0 ; supress page breaks in list file
>   include <p18f4455.inc>
>   include <coff.inc>
>   ; Instruction set extension and Indexed Addressing mode enabledd
>   CONFIG XINST   = ON
>
> vars udata 0x00
> _temp res 1
>
> RESET_VECTOR CODE 00000h ; Reset and Interrupt Vectors
>   pagesel start
>   goto start
> MAIN CODE
>   global start
> start
>
>   lfsr 2, 0xff
>   movlw 0xff
>   ;movff WREG,_temp
>   movwf _temp,ACCESS
>   incf _temp,F,ACCESS
>   incf _temp,F,ACCESS
>   incf _temp,F,ACCESS
>   pushl 0x1
>
> end
> ;============== test.asm end
>
> Thanks
> Siva
>
Subject: RE: gpasm extended mode -- MPLAB message
From: Sivaram Gowkanapalli ####@####.####
Date: 3 Jun 2011 06:33:54 -0000
Message-Id: <SNT125-W34640F3E8EA64543A67674D27F0@phx.gbl>

Marko,
Added to bug tracker: http://sourceforge.net/tracker/?func=detail&aid=3310962&group_id=41924&atid=431665
ThanksSiva

> Date: Fri, 3 Jun 2011 08:54:08 +0300
> Subject: Re: gpasm extended mode -- MPLAB message
> From: ####@####.####
> To: ####@####.####
> 
> No. Comparing the COFF help file from MPASM 5.40 against gpcoff.h,
> flags F_ABSOLUTE and F_EXTENDED18 seem to be missing from the COFF
> file headers. Maybe Microchip has added them at some point but gputils
> has not been updated. These changes in COFF may be part of the changes
> Microchip did while they stopped using COD files.
> 
> I think you should add this to the tracker at sourceforge. If not a
> patch with test cases, a bug report at least.
> 
> Marko
> 
> On Fri, Jun 3, 2011 at 8:14 AM, Sivaram Gowkanapalli
> ####@####.#### wrote:
> >
> > Hello,
> >
> > I built the below file with gpasm and gplink.
> >
> > But, when I import the test.cof file into MPLAB, MPLAB
> > complains with a message of "The Extended CPU Mode Configuration
> > bit is enabled, but the program that was loaded was not built using extended
> > CPU instructions. Therefore, your code may not work properly"
> >
> > I used the --extended flag with gpasm and alos used the latest svn version
> > of gpasm. Just wanted to check if the extended mode of gpasm actually works.
> >
> > ; ============ test.asm begin
> > ; Build commands
> > ; gpasm --extended --object test.asm
> >
> > ; gplink --map --object --output test.hex test.o
> > ;message: using default linker script "/usr/local/share/gputils/lkr/18f4455.lkr"
> >
> >   errorlevel 0
> >   list p=18f4455 ; set processor type
> >   list n=0 ; supress page breaks in list file
> >   include <p18f4455.inc>
> >   include <coff.inc>
> >   ; Instruction set extension and Indexed Addressing mode enabledd
> >   CONFIG XINST   = ON
> >
> > vars udata 0x00
> > _temp res 1
> >
> > RESET_VECTOR CODE 00000h ; Reset and Interrupt Vectors
> >   pagesel start
> >   goto start
> > MAIN CODE
> >   global start
> > start
> >
> >   lfsr 2, 0xff
> >   movlw 0xff
> >   ;movff WREG,_temp
> >   movwf _temp,ACCESS
> >   incf _temp,F,ACCESS
> >   incf _temp,F,ACCESS
> >   incf _temp,F,ACCESS
> >   pushl 0x1
> >
> > end
> > ;============== test.asm end
> >
> > Thanks
> > Siva
> >
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ####@####.####
> For additional commands, e-mail: ####@####.####
> 
 		 	   		  
[<<] [<] Page 1 of 1 [>] [>>]


Powered by ezmlm-browse 0.20.