See your whole system. Debug it together.
Modern embedded systems increasingly distribute functions across multiple SoCs or ECUs. Each SoC may run independently, but the system must still operate as one coordinated whole.
TASKING Multi-SoC Debug and Trace, enabled by the iC7max BlueBox debugger, provides synchronized Run/stop control and a unified trace timeline across multiple SoCs.
Why multi-SoC systems are difficult to debug
A timing violation on one SoC may be caused by an interaction with its synchronized counterpart. Stopping one SoC can trigger a watchdog on a different SoC, while separate timestamps make the original event chain difficult to reconstruct.
A system-level problem needs a system-level view.
How TASKING BlueBox debuggers help
The TASKING iC7max BlueBox debugger connects up to six SoCs simultaneously through TASKING Active Probes. For systems using CAN or LIN bus, the TASKING CAN/LIN Add-on module adds bus communication to the same synchronized timeline, saving time during debugging. The entire session is managed from a single iC7max BlueBox and winIDEA.
- Synchronized run and stop: When one SoC reaches a breakpoint, connected SoCs can be halted together, preserving the system state and reducing watchdog side effects.
- Mixed-architecture support: Debug TriCore, Arm Cortex-A, Cortex-R, Cortex-M, RISC-V, PowerPC, RH850, and other SoC families.
- Unified trace view: Bring events from multiple SoCs together in one synchronized view.
- Flexible profiling options: Combine hardware-based trace, MegaSampling, or SWAT - software trace to analyze runtime behavior across different targets.
- System-level event correlation: Connect SoC activity with CAN/LIN network traffic through add-on modules to understand how processing and communication interact.
Where multi-SoC debug makes a difference
A synchronized view is valuable wherever system behavior depends on coordination between SoCs:
- Automotive: Follow the path from object detection to braking or acceleration in applications such as adaptive cruise control.
- Aerospace: Validate redundant guidance, navigation, and control implementations and inspect voter logic.
- Unmanned systems: Reveal timing violations in flight-control functions distributed across multiple SoCs.
- Humanoid robotics: Analyze synchronized motion controlled by separate SoCs.
See your whole system. Debug it together.
When a system spans multiple SoCs, debugging one SoC at a time can hide the interaction that caused the failure. TASKING Multi-SoC debug and trace brings synchronized control and a shared trace timeline to the full system.