Thanks Bruce!
.... I found the relevant part, but I don't understand it.
I see these code snips...
Code:
@Timer1 = TMR1L
Timer1 VAR WORD EXT
and "re-loading the timer is just as simple as..."
Code:
T1CON.0 = 0 ; stop timer
Timer1 = Timer1 + TimerConst
T1CON.0 = 1 ; turn timer back on
and "another example"
Code:
@Capture = CCPR1L
Capture VAR WORD EXT
In the first example...
@Timer1 = TMR1L
Timer1 VAR WORD EXT
"@" is a straight ASM line, apparently defining "Timer1" to equal TMR1L. Though this says nothing for what TMR1H should be called. The second line Timer1 VAR WORD obviously defines Timer1 as a variable for PBP - and the EXT has something to do with not doing something with it until it compiles - I didn't understand what that post was getting at.
I'm also again seeing in the above post the inter-changing of various forms of hex numbering. I see "1234h" as well as "$1234" and again, I don't understand why you would use the hex in the first place as it's difficult to read - and again my question, is there some way to just write the value you want "12,385" in your code and have PBP turn it into binary or hex as required when compiling? The need to have to "hex" all your integers seems like a complicated additional step and I don't understand what it needs to be done.
Thanks.
Bookmarks