Core specific options
This chapter explains core specific settings. Open Hardware menu / CPU Options / CoreN. Equivalent dialog is provided for each available CPU core.
When checked, the debugger will attach to the core on a debug session start (Reset, Download and Load Symbols). This option is checked by default. In a case the core is not automatically observed from the beginning of the debug session, it is possible observing it at any time later via View / Debug / Session Explorer window.
Note that this option is by default enabled for all available cores. To disable attaching to a specific core on a debug session start go to disable this option in the Hardware menu / CPU Options / Cores / <core>.
This option is not applicable for RH850. All cores are always synced.
This option allows you to configure per-core startup actions.
•Non intrusive - Execution is not obstructed and the core behaves as if in a standalone operation.
•Catch - Stop the core right after initial debug connection (e.g. immediately after it is released from reset).
Preset PC after stopped in init
Preset the PC after a core is stopped during a debug session start. Regardless of the Debug entry type option this option is applicable only for Download and Reset, but not for Attach. Also not used during active debug session, e.g. core stops on software reset catch or low power wakeup.
•No Preset - PC is not preset.
•Entry Point - Presets the program execution point to the program entry point which must be specified in the ELF file.
•Address - Preset to the specified address in the Preset PC address field.
Changing the execution point causes the application to behave differently than when ran without the debugger. This shouldn't be used in normal circumstances. Use with caution after consulting iSYSTEM Technical support.
Preset the PC for a selected address via the Browsing Variables dialog. If you are using a symbol, make sure to select it from the correct boot process.
NMI0, NMI1, RESETZ, WAITZ and HLDRQ CPU input signals can be masked. A masked CPU input has no impact on the CPU behavior, that is, it is ignored.
In case of multi-core devices the dialog is replicated for each core. In RH850 family the first and second core are named PE1 and PE2, respectively. The dialog changes accordingly.