Cross triggering for multicore debugging

The cross triggering provides an option to create a link between different cores during multi-sessional debug. This link allows suspend events on one core to affect other cores.

Note: The S32 Debugger Cross Triggering works only when multi-core debugging is started from a launch group configuration, it does not support multi-core debugging by manually starting debug sessions of two or more cores.
Note: Cross Triggering is implemented for the compute complex cores only. Support for accelerator cores will be added in the future S32DS releases.
Cross triggering control panel is located on the Debug perspective toolbar. It includes the following buttons (from left to right):
(Cross Triggering Configuration) Open the Cross Triggering Configuration dialog to setup core session suspension links between cores applicable to the SoC in the running debug state. This button becomes active upon starting a launch group debugging session.
(Cross Triggering Run) Starts cross triggering on all active debug sessions. Any threads which were suspended will resume. Linked cores may perform suspend events. This button becomes active when at least 1 source and 1 destination is selected within the Cross Triggering Configuration.
(Cross Triggering Enable/Disable) Apply the current cross triggering settings or ignore them if they were already set (depends on current context state). This button becomes active when at least 1 source and 1 destination is selected within the Cross Triggering Configuration.
(Cross Triggering Configuration Erase) Remove the current cross triggering settings, if they were already set. This button becomes active when at least 1 source and 1 destination is selected within the Cross Triggering Configuration.
Note: In addition to the conditions listed above, the buttons will only be active while at least one core is suspended.

The Cross Triggering Configuration dialog presents a list of the SoC's cores which are currently represented in the active debug launch group as well as their current cross triggering link configurations.


Cross Triggering Configuration dialog

Note: A core which is enabled as a source can suspend any of the cores which is enabled as a destination.
Note: A core which is enabled as a destination, can be suspended by any of the cores which is enabled as a source.
After sources-destinations configuration was applied to the SoC the first time, its state is stored inside S32DS user data. When user opens configuration dialog again, its previous checkboxes state will be automatically restored.
Note: Cross Trigger Configuration dialog will be restored to last known state.