I just noticed this.
For some reason, I was thinking the P2 would initialize it's RAM when accepting a new program. That doesn't appear to be happening. If this is documented, I missed it clearly.
Right now, I have the texture sample modified to take values from the HUB, and I'm using an instance of the monitor to modify those for some quick, interactive testing. The values are at $2000, which is my typical place to drop them right now. On program load, they are defined in the COG memory as normal, but on the first frame the reads from the HUB insure they never get used.
When I F10 from Pnut.exe while P2 is running, those values persist. When there is a break in the power, they come up zeroes. I just spent some time trying to figure out why something wasn't working, when it was actually working!
'Fetch new texture values from HUB
reps #6, #1
setptra base 'which is $2000
rdlong INDB++, PTRA++