Sean Schouten wrote:
> I just switched to using the Special Function Registers window as
> opposed to the Watch. I just found that you can actually see 'binary'
> there.

Just like in the watch window.  You can adjust how the VALUE column is
displayed.

> Same thing happened as before. I made one discovery:  The
> W-Register (which contains TEMP_VAR data, as you know) roughly seemed
> to be *following* what the TMR0 register was doing.

Again, could be lack of attention to the bank setting.

> My conclusion was
> that there must be something messed-up with my usage of the RES
> function and thus my memory addressing.

I doubt there is anything wrong with RES, but you do have to consider what
bank variables are in.

> I switched to hard coding the address;

Yecch!  Now that you've got it working, learn to do it right and understand
why the other case didn't work.

> I am now thinking that using RES does not work without having a linker
> script?

Just like the manual says.  However, how did your code ever get built to a
HEX file?

> Can anyone point me to good
> material (tutorial / real world example) on dynamic code and / or
> linker scripts?

The manual (big surprise).  It's called something like MPASM with MPLIB and
MPLINK.

> How does the RES directive work when the assembler / linker sees
> that you have a variable that you must access in two banks? Does it
> register that variable in both banks or do you still have to pay much
> attention to bank switching?

Read the manual before asking such questions.


******************************************************************
Embed Inc, Littleton Massachusetts, (978) 742-9014.  #1 PIC
consultant in 2004 program year.  http://www.embedinc.com/products
-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist