User manual

 iSYSTEM, September 2014 6/23
3 CPU Setup
3.1 CPU Options
The CPU Setup, Options page provides some emulation settings, common to most CPU families and
all emulation modes. Settings that are not valid for currently selected CPU or emulation mode are
disabled. If none of these settings is valid, this page is not shown.
CPU Setup, Options page
Stop CPU Activities When Stopped
When this option is checked, most of the peripheral functions are stopped when the application is
stopped. For details, please refer to the Fx4 User Manual, Chapter 36, On-Chip Debug Unit. This
option directly controls the SVSTOP bit in the EPC Emulation Break Control register. Note that some
peripherals have an override bit to disable stopping when the CPU is stopped in debug mode.
In general, it is recommended that the option is checked in order to have more predictable behavior of
the debugged application using these peripheral functions.
Cache downloaded code only (do not load to target)
When this option is checked, the download files will not propagate to the target using standard debug
download but the Target download files will. This is typically used where the flash memory has limited
number program/erase cycles and when the downloaded code has already been programmed. Don’t
forget to uncheck the option when the program sources have changed!
In cases, where the application is previously programmed in the target or it's programmed through the
flash programming dialog, the user may uncheck 'Load code' in the 'Properties' dialog when specifying
the debug download file(s). By doing so, the debugger loads only the necessary debug information for
high level debugging while it doesn't load any code. However, debug functionalities like ETM and
Nexus trace will not work then since an exact code image of the executed code is required as a
prerequisite for the correct trace program flow reconstruction. This applies also for the call stack on
some CPU platforms. In such applications, 'Load code' option should remain checked and 'Cache
downloaded code only (do not load to target)' option checked instead. This will yield in debug
information and code image loaded to the debugger but no memory writes will propagate to the target,
which otherwise normally load the code to the target.