Where should I discuss SD/MMC FAT issues?

[skimask]

Great! But you where wrong about the 9Tcy... Read previous post again... or build an ASM project then watch the Program Memory window.

And yet again, that's what I get for posting off the hip... Since when is a macro...a subroutine? Must forgive my blatent stupidity...the house payment is due today
So, does that little @ NOP?C trick work any other little way that I'm not knowing of yet with anything else?

BTW...Self-Expanding Macro is my new buzzword...

[mister_e]

So, does that little @ NOP?C trick work any other little way that I'm not knowing of yet with anything else?

Well i don't know.. i'm not in your own short

When you call a Macro, the compiler just copy/paste the whole macro code where you called the macro.

let see...

OneMacro  macro
    MOVE?CT 1,PORTA,0
    MOVE?BB _MyVar,_YourVar
    endm

EACH TIME you call the macro like this...

@ OneMacro

This will paste

    MOVE?CT 1,PORTA,0
    MOVE?BB _MyVar,_YourVar

so...

@ OneMacro
@ OneMacro

will obviously generate

    MOVE?CT 1,PORTA,0
    MOVE?BB _MyVar,_YourVar
    MOVE?CT 1,PORTA,0
    MOVE?BB _MyVar,_YourVar

Hence why we often suggest to reduce your macro size.

in NOP?C, The Conditional While (not sure if conditional or MPASM directive.. but anyway), just copy the amount of NOP you asked in the argument parameter

NOP?C 5

will juste paste
@ NOP
@ NOP
@ NOP
@ NOP
@ NOP

that's it. No code overhead, no nothing.... self expanding... or expandOnDemand ... huh?

[JD123]

Ok, now it's clear and I understnad why it's 5 Tcy for the example. Though it's still going to load tons of NOP's in the code (for my program), it's still strait line. Like you said, it sure will reduce the time needed to tweek the NOP's for clocking speed adjustments. Excelent tip and thanks!

[skimask]

Like you said, it sure will reduce the time needed to tweek the NOP's for clocking speed adjustments. Excelent tip and thanks!

Might even work with a separate variable...as in...
@ NOP?C _variable
? maybe? maybe not?
then you could set the variable at the top and only change it once and in your code use something like
@ NOP?C _variable+2
or
@ NOP?C _variable+10
and so on...
But then again, if you go that far, all you're doing is reinventing the wheel (i.e. pauseus)

[mister_e]

If _Variable is a CONSTANT, it will work indeed. You can still declare it on asm level

@MyVar=.30

and later call the macro

NOP?C MyVar+10

[skimask]

If _Variable is a CONSTANT, it will work indeed.

That's what I meant...a CONSTANT...
I think this little tidbit is going to save me a bunch of typing soon...

[mister_e]

In this case, it could be better to change it too.

ASM
NOP?C   macro Cin
    local a
a=0
    while a<(Cin+MyByte)
        nop
a++=1
        endw
    endm
ENDASM

and at the top of your code you define MyByte like

@MyByte=.10 ; your value.. whatever

[JD123]

When you first typed "=.30", I thought the decimal and the zero were a type-o. Then I see you used "=.10". It's been a long time (close to 10 years ago) that I've been through the MPASM manual, and I can still go back and read it, but can you explain the "=.30" and "=.10" for defining 3 and 1? I would have thought it would just be "=3" or "=1".

Thanks for taking your time to explain all this to us.

[mister_e]

It's just a MPASM naming convention. Depending the current MPASM radix setting
@a=10
@B=30
Those above could be considered as decimal or hexa.

Let's open a PBP .INC file, let's say 16F628.inc, you'll discover...

    else
        LIST
        LIST p = 16F628, r = dec, w = -302
        INCLUDE "P16F628.INC"   ; MPASM  Header
        ;__config _XT_OSC & _WDT_ON & _PWRTE_ON & _MCLRE_ON & _LVP_OFF & _CP_OFF
        NOLIST
    endif
        LIST

so every value should be considered as decimal using PBP.

MPASM naming convention
.10 or d'10' will always be considered as 10 decimal whatever your Radix setting is.. kinda safe way to write things.

[JD123]

Thanks Mr.E. Now that you mentioned it, I remember dealing with the radix before, but never much explored it many uses. Again, that was a long time ago... and I've had several beers since then.

[mister_e]

oh... think we ALL had few beer... in case you're thirsty

[skimask]

oh... think we ALL had few beer... in case you're thirsty

Well, in that case, I'll take
@MyBeer=.12
(of course that's 30 in metric beers...double it and add six)

Handy tip there MrE...

[mister_e]

if i could .. i would put...

MOVLW .3
MULLW .8
MOVFF PRODL, _InMyThroat

or so