gnupic: Re: [gnupic] Possible gpasm or gplink bug?
Subject:
Re: [gnupic] Possible gpasm or gplink bug?
From:
Craig Franklin ####@####.####
Date:
16 Nov 2005 01:28:54 +0000
Message-Id: <437A8A4E.6050503@users.sourceforge.net>
Chen Xiao Fan wrote:
>>I just tried one simple example and MPASM/MPLINK is okay with
>>Julian's method. RAM variable address is resolved correctly
>>at link time even though it is not availabe at the assemble
>>pass.
>>
>>So Julian may be correct that this is a bug with gpasm/gplink.
>>
>>
>
>I tried the same example using gpasm/gputils, gpasm/gputils
>produce the correct results just like MPASM/MPLINK.
>
>...
> UDATA_SHR
>WTEMP res 1 ; register used in Interrupt Routine
>...
>movlw WTEMP -->
>...
>
>00007d 3025 MOVLW 0x25 movlw WTEMP (for MPASM/MPLINK)
>00007d 3020 movlw 0x20 movlw WTEMP (for gputils)
>
>Maybe Julian could post more details. A wild guess
>is that the RAM address is running out.
>
>
>
It should generate an error in that case. You are right, seems like the
problem is elsewhere. What linker script are you using?
>Regards,
>Xiaofan
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: ####@####.####
>For additional commands, e-mail: ####@####.####
>
>
>
>
