To set up cross-triggering for multiple processors:
Select Target ? Synchronization Control... to display the Synchronization Control window, shown in Figure 6.14.
Expand the connections for the processors that are to take part in cross-triggering, shown in Figure 6.15. This shows the cross-triggering controls for each processor (see Cross-triggering controls).
Decide which processors are to take part in cross-triggering. Also, decide which processor is to have the
Outtrigger set, that is, the one that is to have control over the other processors. The remaining processors that you want to use for cross-triggering have theIntrigger set.Note
More than one processor can have the
Outtrigger set, or both theOutandIntriggers set.Click the check box to set up the Out-In trigger relationships:
- In
The processor is to respond to the stop request of a processor that has the Out check box enabled.
- Out
When the processor stops, it is to broadcast a stop request to processors that have the In check box enabled.
If a processor does not have either In or Out selected, that processor does not participate in cross-triggering.
In the example shown in Figure 6.15, when the ARM920T™ processor stops, then the ARM940T processor stops. The simulated processor,
Simarm_0, is not affected by the cross-triggering of the other processors.Load the required images, and set up the debugging conditions for your targets. For example, set any breakpoints.
If the processors are not synchronized, as in this example, then start the processors as follows:
Start each processor that has only the
Intrigger set (for example, the ARM940T).Start each processor that has the
Outtrigger set (for example, the ARM920T).Note
If more than one processor has the
Outtrigger set, then perform a synchronized start for these processors.
You can start unsynchronized processors using one of the following methods:
start the processor for the current connection, then cycle to the next connection (see Changing the current target connection)
display multiple Code windows, attach each Code window to a different connection, then start the processors from each Code window (see Attaching multiple Code windows to different connections).
Alternatively, set up a synchronized start, so that all the synchronized processors start together when you start one of the processors (see Synchronizing multiple processors). Also, make sure that the synchronized stop operation is disabled.
Note
If your hardware supports more complex cross-triggering controls, you must set these manually. Alternatively, you can create a script to set the appropriate configuration. For example, if your hardware supports the Embedded Cross Trigger unit, see Configuring embedded cross-triggering for a connection.
PDF version