Multi-SoC Synchronization
In this topic:
•BlueBox Sync configuration options
Introduction
The FNet Bridge Multi SoC synchronization enables the coordination of two separate BlueBox Debuggers via the FNet communication network. This setup facilitates synchronous debugging and tracing across multiple systems, achieving low latency synchronization typically within a few microseconds.
Requirements
•2x iC7max/iC5700 BlueBox Debuggers with Hub
•2x Active Probes
•(optional) ADIO or/and CAN/LIN Add-on module(s)
Limitations
•Delays for the Basic sync are less than 10 miliseconds.
•Delays for the Advanced sync are in the range of microseconds.
•Advanced Sync Debug is supported only for Infineon TriCore systems.
BlueBox Sync configuration options
The BlueBox Sync dialog allows you to set up and manage synchronous debugging of multiple winIDEA Workspaces (for example, when debugging two or more SoCs in sync).
It defines which workspace acts as the synchronization Master and which act as Slaves, as well as how timing and configuration data are shared between them.
Access this dialog via Hardware | Options | BlueBox Sync.
Synchronization
Synchronization mode - Determines whether the current winIDEA instance operates as the Master or a Slave in the synchronization setup.
•This winIDEA instance is synchronization master – Select this option for the Master workspace.
•This winIDEA instance is synchronization slave – Select this option for Slave workspaces.
Synchronize time - When enabled, synchronizes the timestamps between Master and Slave BlueBoxes, ensuring aligned timing across devices.
Preset Probe and SoC Configuration - Applies a preconfigured setup to all connected BlueBoxes.
Slave Workspaces
This section lists all Slave winIDEA workspaces associated with the Master.
Each entry defines a workspace file and an optional command-line parameter for automation or specific startup configurations.
Synchronized trace operation
The synchronized debug start/stop operations and trace clock propagation through FNet ensure that both systems operate in a coordinated manner, essential for accurate and efficient system analysis and debugging. Performing a synchronized trace recording requires the following steps:
1.Alignment of BlueBox Time Offset - This is needed for the trace visualization in the Profiler Timeline View. The Time Offset alignment aligns the time offset from time 0 to the first trace recording in each Profiler Timeline. It does not influence the overall trace synchronization accuracy.
2.Start of both Trace Recorders - The operation starts the generation of trace messages on the target. However, as the BlueBox recorder is set to ON Trigger, the BlueBox will not record any trace data until the occurrence of the Trace Trigger.
3.Trace Trigger - A trace trigger can be injected either on the Slave or on the Master winIDEA instance. The trigger is propagated via FNet to both the Master and Slave BlueBox trace recorder. The propagation delay of the trace trigger via FNet does not influence the overall trace synchronization accuracy.
Block diagram below shows that the Trace Trigger is propagated through the entire system via FNet. The Trace Clock is also propagated to all trace recorders. Synchronized debug start/stop operations are controlled via FNet as well.
Synchronized Trace Operation overview
More resources
•Sync Debug on two Infineon AURIX devices - How-to guide
•Sync Trace - How-to guide
•Timing Analysis Across Two ECUs with winIDEA & BlueBox Tools - Webinar
