HP 64783A, User Manual

Page: 420 / 816

deMMUer, or Out of DeMMUer resources, because the deMMUer might run out of
resource blocks before all of the physical addresses have been assigned reverse
translations, but the program spaces you care about will all be reverse translated.
You can use the verbose option of the deMMUer load command to make sure the
program spaces you care about will be reverse translated.
If you map a space greater than 256 Mbytes in the emulation memory map, you
will run out of resource blocks before you satisfy the map.
The best way to ensure that all of the address ranges you care about will be reverse
translated is to compose an emulation memory map that allocates blocks of
physical memory only large enough to accommodate the address space occupied by
code you are trying to develop. The deMMUer algorithm will allocate resource
blocks in its eight-entry table to reverse translate only those physical address ranges.
With the above example, you could have avoided running out of resources. If you
had placed invalid descriptors in your MMU tables in the paths that lead to unused
physical address ranges, the deMMUer would have had more than enough resource
blocks in its eight-entry table to reverse translate the valid address ranges.
Finally, you can store the present setup of the MMU to a file, and then use an editor
to eliminate address ranges that do not need to be reverse translated. This only
leaves address ranges that need to be reverse translated in the file. Then you can
load this file into the deMMUer. When this file is loaded, the deMMUer creates a
set of reverse translations for it, ignoring the MMU setup in the emulator. Refer to
"Saving and Restoring DeMMUer Setup Files" in Chapter 3, "Using the
Emulation-Bus Analyzer", for how to store and load a deMMUer file.
Chapter 10: Using Memory Management
Using the DeMMUer
390