Searching \ for 'Re[3]: 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[3]: reference card'
1997\02\19@145940 by Craig Knotts

flavicon
face
    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 <spam_OUTScott.FinkTakeThisOuTspamMICROCHIP.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@124909 by Dwayne Reid

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

And I hope they continue to be supported.  The single instruction pseudo ops
are invaluable in making the code easier to read (skpz, skpnc, etc).  In
addition, if Mchip decides to make a new part where the status flags are in
different locations from the old parts, code using those pseudo ops will
still work since the assembler knows where the flags are for each particular
device.

I do find the multi instruction ops (bz, bnc, etc) useful also, but always
make sure that they are not used following a conditional test.



Dwayne Reid   <.....dwaynerKILLspamspam@spam@planet.eon.net>
Trinity Electronics Systems Ltd    Edmonton, Alberta, CANADA
(403) 489-3199 voice     (403) 487-6397 fax

1997\02\20@221106 by Eric Smith

flavicon
face
> I do find the multi instruction ops (bz, bnc, etc) useful also, but always
> make sure that they are not used following a conditional test.

In principle, an assembler should be able to generate a warning for that.
There should even be something you can put in your own macro definitions
to trip the warning if the macro is invoked after a conditional.

I'm so frustrated with MPASM that I'm writing a replacement; I'll have to
put that feature in mine.  Along with the $1b syntax for hex constants, and
true bit equates.

Eric

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