[weblacky]

Also, I should add -- I don't know that the POD commands will help.  They can read/write values in memory, or otherwise mapped to memory.  But this is stored on some kind of nvram, which is not necessarily going to be mapped in a way that can just be written directly.  But, for example, I suspect if you read a doubleword via POD commands at 0x9000000100000068 I think you'll find 0x69703237636f6e66 .  (in other words, "ld 0x9000000100000068" should read that number,  or "la 0x9000000100000068" should show you "i p 2 7 c o n f").  But I don't know if that's the actual in-flash values (unlikely), or copied into memory at boot (more likely?)

The intention isn't permanency.  The intention is...OHHH GAWD MY PIMM IS GONE AND THIS NEW ONE IS THE WRONG SPEED AND MY BOARD IS TRAPPED...cough...cough...

The memory is usually copied from native storage into some kind of working storage, it's the change of this working storage that gets your mainboard boot with "hacked" CPU values...so you can then flash the REAL natives one and have a working fuel under Irix.  Trapped Fuel mainboards are always an issue.  POD mode was the "suggested" promise that perhaps you can do the change on a system where you're already painted into a corner.

I'd like to think a programmer would simply map or intake the entire struct into memory and work with it...so perhaps there is a way of scanning using the POD commands for the identifying string you've found by using the Print Address function?

I get your point, they MAY have done a read-only mapping into EPROM to read the values, or who knows where they are copied to...and if they are mapped there may not be a "write" function to hold a copy in the mapping technique.  But a part of them thinks they'd HAVE to else all their diagnostic and advanced commands would be meaningless as they could not change anything for testing...which is actually was POD is for!?  So I'd like to think ALL these memory commands must be in working memory (ignoring native storage) and they may not be aligned to these prom offsets.

All good points, we're in the unknown after all.  But I'd hazard a guess it's worth the time to see what happens when you "get" a value that you want and try to "set" that same value and see if it takes and if it does...does it persist or does it change change working memory and native storage is unaffected?

Interesting stuff.