[ChrisA]

oops i meant to put 64... ooh well
also forgot about the part that there is only one set of scratchpad ram which is what you have to use to share values with the other banks

anyways i would go with you on that programming error (which is what we thought it was at first) but when we took that var and changed its location (no there werent 2 vars using the same location, we did check that) it worked exactly how it was supposed to. weve had this happen at least 3 times and it definitly is the locations because weve tried different vars in a couple of those locations. like i said we spent like a couple hours debugging the code to find that that was the problem. id post a piece of code to show you that its fine but i dont have the code at my home computer.

the pattern as i remember it is always a pattern of numbers that sequentially run (0,3,2,1,0,3,2,1...) i think we had a pattern like 35,38,37,36...also but they dont really seem to relate to any values that we give it. (this is just one memory location which we are writing a value to then reading the value and finding it not to be the value we put there) an example, we were setting all of our drive wheels to the same value in the code...
(we changed it to look something like this for debuggin purposes)
PUT s_lf_wheel, 127
PUT s_rf_wheel, 127
PUT s_lb_wheel, 127
PUT s_rb_wheel, 127
upon reseting, after having downloading the new code to the rc, we found that the value for one of the wheels was running 0,3,2,1... while all the others (which had the same values) were stopped (at 127 as they should have been)

this whole thing has spooked us and we really dont know what to make of it. all we do know is that we cant use those locations otherwise well get some really really weird values.

maybe this will make some sense out of the issue for you (if you can understand what ive written here)

note: all scratchpad ram locations relating to pwms are set to 127 upon reset by a piece of our code