Initialization before Programming, Debug Session, at Attach
winIDEA can execute initialization at these events:
•Initialization before Programming
•Initialization before Debug Session
Open Hardware > SoC Options > Reset.
Initialization before Programming
After CPU emulation is started and CPU is stopped the initialization is typically used to prepare the system for programming. This initialization can be invalidated after program completes (the CPU is reset again). This way the CPU starts in a standalone mode, but with a re-programmed memory.
|
CPUs that cannot be stopped immediately after released from reset, are not initialized until they are stopped. Refer to the separate technical notes that came with your system for more information. |
To execute this operation perform Program.
Connect - Actions needed to establish debug connection.
Initialize - Actions needed to initialize device peripherals.
Reset CPU after program (invalidates initialization) - If this option is checked, the CPU is reset after program completes. This effectively invalidates the initialization (which was used to allow program) and provides the CPU with an environment equal to standalone operation (without debugger attached). Not used during development when loading applications and running them from volatile memory, e.g. SRAM. Initialization before Debug Session is always performed except on Program with Reset after Program unchecked.
Initialization before Debug Session
Initialization after program program completes is used when the main initialization is invalidated by a SoC reset after program, but some initialization is still required.
To execute this operation perform Reset.
Initialization before Programming with enabled option Reset CPU after program (recommended).
Initialization at Attach
Initialization at Attach is used when winIDEA is connecting to already running system, i.e. target is not reset by BlueBox. It was introduced for existing INI scripts which can not -if-else- on the type of an 'attach' winIDEA is executing. Same could be achieved in EVE script in Initialization before Debug because it is called with a parameter specifying the reason for execution.
To execute this operation perform Attach.
