Table of Contents
Advertisement
Error Messages
Load completed with errors
Cause: While loading a file into the emulator, one or more events occurred
that caused errors during the load process.
Action: Use the display error_log command to view any errors. You may need
to modify the configuration and map memory before you load the file again. If
the problem persists, make sure the host system and emulator are operating
properly, and that you are trying to load an acceptable file.
Logical emulator name unknown; not found in 64700tab file (10315)
Cause: This message may occur while trying to start up the emulator. It
indicates that the emulator name specified could not be found in the
64700tab.net or /etc/hosts files.
Action: Specify the name in one of these files.
Map term n limited to 4 chip selects (165)
Cause: This status message occurs if more than 4 chip selects are assigned to
a mapped term (as defined by the EMSIM registers: EMCSOR[0-10],
EMCSBR[0-10], EMCSORBT, or EMCSBRBT). Only the first 4 chip selects
will be allowed.
Measurement system not found
Cause: You tried to end the current emulation session and select another
measurement system module which could not be located by the host system.
Action: Either try the end select measurement_system command again or
end and release the emulation session.
Memory allocation failed, ending released
Cause: This is a fatal system error because the emulation session was unable
to allocate memory.
Action: You may need to reconfigure your UNIX kernel to increase the per
process maximum memory limit and available swap space. Reboot your
UNIX system and try starting a new session again.
Memory block list unreadable
Memory mapping not allowed in ACT mode (154)
Cause: When the emulator is in ACT mode the memory system is disabled.
Therefore, you cannot map memory.
468
Advertisement
Table of Contents
