Scott wrote:
> >         lfsr    0,arr
> >         movf    i,w
> >         movff   x,plusw0
> =

> Exactly! In fact, this is the only "legitimate" use I've found for the
> "movff" instruction. I suppose you can argue that "movff" doesn't affec=
t
> WREG... But it still takes two cycles (and two program memory words) ju=
st
> like a 16x style move would.

Another advantage of MOVFF is that it can directly access the entire 4K
memory space without concern for banking.  This could be a significant co=
de
savings in a program that uses more RAM than can be directly accessed (38=
4
bytes, I think).
        Jason Harper

--
http://www.piclist.com hint: To leave the PICList
mailto:piclist-unsubscribe-request@mitvma.mit.edu