HP Forums
Revisiting: Poking a value into address 4100 (NoV-32/HP-41) - Printable Version

+- HP Forums (https://archived.hpcalc.org/museumforum)
+-- Forum: HP Museum Forums (https://archived.hpcalc.org/museumforum/forum-1.html)
+--- Forum: Old HP Forum Archives (https://archived.hpcalc.org/museumforum/forum-2.html)
+--- Thread: Revisiting: Poking a value into address 4100 (NoV-32/HP-41) (/thread-136773.html)



Revisiting: Poking a value into address 4100 (NoV-32/HP-41) - Geir Isene - 04-30-2008

Ok, revisiting a topic partly covered a few months back.

Given that I have a POKE function in the "fixed" part of a NoV-32, how do I make it write to the address 4100 to make it switch the HEPAX ram blocks?


Re: Revisiting: Poking a value into address 4100 (NoV-32/HP-41) - Raymond Del Tondo - 04-30-2008

Looking at CPU reg C:

You will use the nibs 6543210 of C, nibs [6:3] are always used as

address field, and nibs [2:0] are (almost) always used as data field.

For more details, please take a look into the SDK41 manual.

Here's a code snippet which may be of help.

R= 6

LD@R 4

LD@R 1

LD@R 0

LD@R 0 (note that the active pointer will be decremented automatically after the LD)

LDI S&X hhh (where hhh is the HEX val you want to write)

WROM

That's it;-)

HTH

Raymond


Re: Revisiting: Poking a value into address 4100 (NoV-32/HP-41) - Diego Diaz - 04-30-2008

Hi Geir,

Although some people might think the opposite way, I'm *not* the most authoritative person to respond this question... mostly because I have no idea of the supposed behavior of that POKE function.

Assuming it does what every other POKE I've ever seen does. It will fill the given address with the given contents... right?

Ok, then simply place an H'000 into H'4100 to turn RAM block 0 (zero) on, or H'001 to turn on block 1 (one).

Anyhow, I'll have to check de NoV-32 code to confirm if this will work into a running program, or you'll need to go to "stand by" (set PWO line Low) to physically achieve the block swapping. Should this was the case, chances are that NoV-32 internal code would have to be modified to get RAM block swapped "on the fly". Yes, if we reach that point I may well be the most auhoritative person for the job... (well... er... hope so ;-))

Best wishes.

Diego