I don't follow.

     On the 16C5x, at least, NOP is 0x000, while movf 0,w would be 0x200
     and movwf 0 would be 0x020.  The only thing that NOP might code to
     would be tris 0, which is of course a nonsense operation.


______________________________ Reply Separator _________________________________
Subject: Re: Instruction encodings (was: Code error)
Author:  John Payson <supercat@MCS.NET> at Internet
Date:    2/21/97 9:07 AM


> The PIC is an interesting case - have a look at the encoding for NOP - it
> happens to be equivalent to
>
>         movwf   0,w
>
> NOP even gets listed in the opcode table with the other instructions that
> reference memory. Go figure.

Right.  What happens if FSR happens to be pointing at a register which would
be affected by the read?