> So my program may contain several macros in a row, like:
>
>      ldw    Ticks,1
>      ldw    Seconds,60
>      ldw    BlinkValue,15
>
> I can see the
> program counter very helpfully (ahem) toggling between the first and
> second line of the macros in my MACROS.I file, but I can't see which
> of the macros is being executed.
>
I write code the same way.  When I'm not pressed for execution speed
or program memory, I'll put a NOP before a macro, when I need to know
which macro is executing right this minute.  These can be taken out
as things get tighter.   I use a lot of other extra
statements during debugging anyway, so this doesn't seem any
different.

For instance I'll use
TEST  EQU   1

WAITASEC
          If TEST = 1
             goto ENDWAIT
          ENDIF
< ONE SECOND DELAY>
ENDWAIT
                ENDM


As a way of bouncing out of tedious time delay macros during
debugging.  These statements are easy to turn off by making TEST EQU
0 at compile time.






--------------------------------------------------------
> ---- Frank A. Vorstenbosch                           Phone:
> +44-181-636 3391 Electronics & Software Engineer
> or:  +44-181-636 3000 Eidos Technologies Ltd., Wimbledon, London
>  Mobile:  +44-976-430 569
Best Regards,

Lawrence Lile