Table of Contents
Advertisement
Restrict to real-time
runs?
Caution
4-4 Configuration the Emulator
yes
When reset to monitor is selected, the emulator will
be running in the monitor after configuration is
complete. If the reset to monitor fails, the previous
configuration will be restored.
no
After the configuration is complete, the emulator
will be held in the reset state.
The "restrict to real-time" question lets you configure the emulator so
that commands which cause the emulator to break to monitor and
return to the user program are refused.
no
All commands, regardless of whether or not they
require a break to the emulation monitor, are
accepted by the emulator.
yes
When runs are restricted to real-time and the
emulator is running the user program, all
commands that cause a break (except "reset",
"break", "run", and "step") are refused. For
example, the following commands are not allowed
when runs are restricted to real-time:
Display/modify registers.
Display/modify internal I/O registers.
Display/modify target system memory.
Load/store target system memory.
If your target system circuitry is dependent on constant execution of
program code, you should restrict the emulator to real-time runs. This
will help insure that target system damage does not occur. However,
remember that you can still execute the "reset", "break", and "step"
commands; you should use caution in executing these commands.
Advertisement
Table of Contents
