Searching \ for 'Re[4]: reference card' in subject line. ()
Make payments with PayPal - it's fast, free and secure! Help us get a faster server
FAQ page: techref.massmind.org/techref/index.htm?key=reference+card+RE%5D
Search entire site for: 'reference card'.

Truncated match.
PICList Thread
'Re[4]: reference card'
1997\02\19@163526 by Scott Fink

flavicon
face
    I stand corrected.  I was looking at rev D, they decided to cave and
    put them back in rev E. But my main caution about knowing what they
    REALLY do stands.  Take for example:

    Psuedo OP:         Compiles to:
    ADDCF f,d          BTFSC 3,0
                       INCF  f,d

    In this case two instructions are compiled for one pseudo-op.  Again,
    using only the native instructions is the safest course.

    Scott


______________________________ Reply Separator _________________________________
Subject: Re[3]: reference card
Author:  Craig Knotts <spam_OUTCraig.KnottsTakeThisOuTspamCCMAIL.CARRIER.UTC.COM> at Internet_Exchange
Date:    2/19/97 2:56 PM


    Considering the latest MPASM manual (release E) includes these
    pseudo-ops, it would appear that they ARE documented and officially
    supported.


______________________________ Reply Separator _________________________________
Subject: Re[2]: reference card
Author:  Scott Fink <.....Scott.FinkKILLspamspam@spam@MICROCHIP.COM> at Internet
Date:    2/19/97 12:08 PM


    Brian,

    It is OK to use these "hidden" instructions like skpnz as long as you
    remember that they are actually MPASM pseudo-ops and that some of them
    assemble to multiple op codes (i.e. take more than one instruction
    cycle).  The only "real" instructions are those listed in the
    datasheets.  I have talked to a lot of people who have problems because
    they forget which are op-codes and which are pseudo-ops and their
    timing loops come out wrong ("the PIC must be missing a clock or
    something", wrong, you used a multiple instruction pseudo-op).

    You may also note that they are no longer documented in the MPASM
    users guide and are not therefore officially supported or guaranteed
    to work on future versions.  Use caution when using them.

    Best Regards,
    Scott

1997\02\20@062416 by mike

flavicon
picon face
In message  <00004C54.1332spamKILLspamccmail.microchip.com> .....PICLISTKILLspamspam.....MITVMA.MIT.EDU writes:
>      I stand corrected.  I was looking at rev D, they decided to cave and
>      put them back in rev E. But my main caution about knowing what they
>      REALLY do stands.  Take for example:
>
>      Psuedo OP:         Compiles to:
>      ADDCF f,d          BTFSC 3,0
>                         INCF  f,d
>
>      In this case two instructions are compiled for one pseudo-op.  Again,
>      using only the native instructions is the safest course.
>

The one that catches me out is when I skip past a 2 instruction
pseudo-op. eg:

       btfss   FileReg, x
       addcf   f, d
       ...

compiles to:
       btfss   FileReg, x
       btfsc   3, 0
       incf    f, d

Which is not what I wanted to do at all :-)

That said, I think that  skpnc is MUCH clearer to read and
understand than btfsc status, c.



Regards,


Mike Watson

More... (looser matching)
- Last day of these posts
- In 1997 , 1998 only
- Today
- New search...