|Non-Confidential||PDF version||ARM DUI0842F|
|Home > Target Connection Mechanism > Disconnecting from a target > Typical shutdown scenarios|
This section describes the typical scenarios for shutting down a simulation.
A single connected caller initiating a simulation shutdown is the most typical scenario.
Release()call to the simulation with either
shutdownparameter value. Depending on the parameter value, the simulation is destroyed or kept alive.
The simulation initiates its shutdown and informs the caller.
simShutdown()callback through the registered simulation callback object.
Release()call to indicate that it does not access the simulation or targets in the future.
false, as the simulation is already shutting down. A value of
trueis ignored at this point.
The sequence is similar to that for a single caller that initiates shutdown except that the other caller must also be shut down.
Release()method for the simulation. The
shutdownparameter can be either
false, the simulation is not shut down and the sequence ends here.
true, there is a requirement for some interaction with all other attached callers. To indicate the demand to shut down, the simulation issues the
simShutdown()callback to all registered simulation callback objects that are enabled for this call.
Release()call to announce successful disconnection from the simulation. Its
shutdownparameter is set to
falseas the shutdown is already in progress (a value of
trueis ignored at this point).
CADISimulationobject can be destroyed.
simKilled()callback. If this occurs, the caller must not access the corresponding simulation in the future.
Multiple callers are attached to a simulation and the simulation initiates its own shutdown.
simShutdown()callbacks to all attached callers that have registered a simulation callback object.
Release(). After all attached callers are signed off, the simulation can be safely destroyed.