Where should I discuss SD/MMC FAT issues?

[mister_e]

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

[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...