> You are right, that is how I figured it out. By checking the files in
> the watch window. I initially was looking for the fault in the wrong
> place, thinking the fault was with the bit test. And since I was using a
> two word instructing like movff for the first time, I then really got
> confused. But it is confusing when the debugger shows that it is going
> to execute the movff instruction when it is not.

But where else should it be indicating when executing the second half of
the MOVFF as a NOP?  Pointing either the next or previous instructions
would be less correct.


*****************************************************************
Embed Inc, embedded system specialists in Littleton Massachusetts
(978) 742-9014, http://www.embedinc.com

--
http://www.piclist.com hint: The list server can filter out subtopics
(like ads or off topics) for you. See http://www.piclist.com/#topics