gnupic: Re: [gnupic] Possible gpasm or gplink bug?


Previous by date: 14 Nov 2005 00:48:36 +0000 Re: MCHPFSUSB AN950, AN956, ..., John Swensen
Next by date: 14 Nov 2005 00:48:36 +0000 Re: [gnupic] Possible gpasm or gplink bug?, Scott Dattalo
Previous in thread:
Next in thread: 14 Nov 2005 00:48:36 +0000 Re: [gnupic] Possible gpasm or gplink bug?, Scott Dattalo

Subject: RE: [gnupic] Possible gpasm or gplink bug?
From: Chen Xiao Fan ####@####.####
Date: 14 Nov 2005 00:48:36 +0000
Message-Id: <3B8AEFFADD3DD4118F8100508BACEC2C0A2893A6@spex>

>From: Julian Green 
>Sent: Saturday, November 12, 2005 9:28 PM
>To: ####@####.####
>Subject: [gnupic] Possible gpasm or gplink bug?

>The code Im doing is fairly simple:
>
>    movlw  msg_to

Wait a moment, msg_to should be a literal here.

>    addwf  RxState, w
>    movwf  FSR
>
>msg_to - is defined as:
>
>    serial_u   udata_shr
>    msg_to	res 1

msg_to is now a ram variable. What should gpasm assume?
The code is wrong.

I think "movlw msg_to" should be "movf msg_to,w".




Previous by date: 14 Nov 2005 00:48:36 +0000 Re: MCHPFSUSB AN950, AN956, ..., John Swensen
Next by date: 14 Nov 2005 00:48:36 +0000 Re: [gnupic] Possible gpasm or gplink bug?, Scott Dattalo
Previous in thread:
Next in thread: 14 Nov 2005 00:48:36 +0000 Re: [gnupic] Possible gpasm or gplink bug?, Scott Dattalo


Powered by ezmlm-browse 0.20.