gnupic: Re: [gnupic] Stupid question
Subject:
Re: [gnupic] Stupid question
From:
Craig Franklin ####@####.####
Date:
15 Feb 2005 05:50:55 +0000
Message-Id: <42118E54.5010300@users.sourceforge.net>
Adam Wozniak wrote:
>Bueller?
>
>Or is this just not ready for anyone to play with yet?
>
>
>
Correct.
>On Thu, 10 Feb 2005, Adam Wozniak wrote:
>
>
>>I can't seem to figure out what I'm doing wrong here...
>>
>>[awozniak@mauve tmp]$ gpal --version
>>gpal-0.13.0 pre-alpha
>>
>>[awozniak@mauve tmp]$ cat p5.pal
>>
>>module P5 is
>> procedure main is
>> begin
>> null;
>> end procedure;
>>
>> procedure isr is
>> begin
>> null;
>> end procedure;
>>end module;
>>
>>[awozniak@mauve tmp]$ cat p5.pub
>>
>>public P5 is
>> pragma code_section="page";
>> procedure main;
>> procedure isr;
>>end public;
>>
>>[awozniak@mauve tmp]$ gpal -p p12f675 p5.pal
>>
>>p5.asm:11:Warning [205] Found directive in column 1.
>>p5.asm:11:Error [127] Too many arguments.
>>p5.asm:17:Error [152] Executable code and data must be defined in an
>>appropriate section.
>>p5.asm:18:Error [152] Executable code and data must be defined in an
>>appropriate section.
>>p5.asm:23:Error [152] Executable code and data must be defined in an
>>appropriate section.
>>p5.asm:24:Error [152] Executable code and data must be defined in an
>>appropriate section.
>>
>>
>
>
>
Errors are being generated in the assembly phase (p5.asm). When this
happens run the compiler with the -S flag. That will cause the assembly
file to be generated, but not assembled. Then debug the file.
pragma code_section="page";
Is causing a section with the name "page" to be generated. page is a reserved word for gpasm. Here is a segment from the linker script:
CODEPAGE NAME=page START=0x0 END=0x3FE
...
SECTION NAME=PROG ROM=page // ROM code space
You should be using "PROG" instead of "page".
The next problem you will have is that gpal using udata sections for data memory. The 12f675 linker script only defines udata_shr. This is a real bug, I will put on my TODO list.
