CombiProbe Compact Trace
Compact Debug and Trace Tool for Mid-Range Embedded Systems
Leverage the power of a full trace system geared towards your mid-range embedded design. The CombiProbe 2 is a compact debug and trace system that provides our full feature set to embedded systems with compact trace ports of up to 4 bits wide.
Utilize the Power of Both Debug and Trace
Our CombiProbe 2 is your perfect companion if you need full insight into what your embedded system is doing at run-time. Besides its comprehensive debug capabilities, it can capture real-time information like system traces and some compact parallel flow traces, which are essential for system profiling or safety certification. Trace recording often helps you launch your product faster and with more confidence.
Debug and Trace Two Multi-Core SoCs at the Same Time
With dual multipurpose connectors, our CombiProbe 2 enables you to debug and trace two independent multi-core SoCs at the same time.
Implement Numerous Architectures and Thousands of Devices
Our CombiProbe 2 supports thousands of device series from most major CPU architectures, including Arm Cortex, RISC-V, Infineon TriCore, Intel x86, dsPIC and MIPS. This vast range of support lets you easily switch from one chip and supplier to another while keeping the same CombiProbe 2 and user interface.
Capture Everything with Ultra-Long-Duration Trace
Long-term trace data recordings can be streamed to your host PC for later analysis. An average streaming speed of 140 MB/s ensures reliable transfers without data loss.
Profile your AUTOSAR Adaptive Platform
Our CombiProbe 2 is the perfect tool to profile your AUTOSAR Adaptive-Platform-based operating system. Together with our ARTI kernel driver, the CombiProbe 2 can capture task state information to visualize runtime statistics and timing charts.
Observe Your SoC from the Inside and Outside
In conjunction with the Mixed-Signal Probe, our CombiProbe 2 can sample analog and digital signals over time as well as decode the protocols sent via digital lines. If your SoC supports a suitable flow trace, the recorded signals can be correlated, giving you a clear, detailed, time-aligned view of the processor state along with its I/O signals.
Simplify Energy Profiling
Our CombiProbe 2 and Mixed-Signal Probe together can measure and record the power consumption of your embedded system over time. If you SoC supports a suitable flow trace, the power consumption can be correlated with the program flow, enabling you to efficiently profile your application’s power consumption and optimize any power-hungry code sections.
Compare Trace Extensions
|Product||µTrace for Cortex-M||CombiProbe 2
||PowerTrace II Lite
||PowerTrace III||PowerTrace Serial 2|
|Memory Size||256 MByte||512 MByte||1 GByte||Up to 8 GByte||Up to 8 GByte|
|Max. Trace Port Width||4 parallel lines||Two ports with 4 parallel lines||32 parallel lines||32 parallel lines||8 serial lanes|
|Max.Recording Speed||400 Mbit/s per line||400 Mbit/s per line||450 Mbit/s per line @ 17 lines||600+ Mbit/s per line @ 17 lines||22.5 Gbit/s per lane @ 4 lanes|
|Max. Streaming Performance 1
(Peak / Average)
|up to 200 / 140 MByte/s||200 / 140 MByte/s||1.350 / 100 MByte/s||2.400 / 400 MByte/s||10.000 / 400 MByte/s|
|Option for Energy profiling||Via Mixed-Signal Probe||Via Mixed-Signal Probe||Not Available||Via Mixed-Signal Probe||Via Mixed-Signal Probe|
|Required debug module||-||Any PowerDebug2||PowerDebug X503||PowerDebug X503||PowerDebug X503|
||See more||See more|
1 The streaming rate defines the amount of data which can be transferred on the fly to the PC per second. If the trace-port rate is below the streaming rate in average, a practically infinite recording time is possible. The peak-rate is possible temporarily and is compensated by the internal memory of the CombiProbe.
2CombiProbe 2 works with PowerDebug X50, E40, PRO, USB 3, II. Not supported are PowerDebug Ethernet, USB, USB 2.
3 PowerTrace extensions work with PowerDebug X50, PRO, II.
Connect Your Target Optimally with Your CombiProbe 2
A whisker is the physical link from your target's debug and trace port to your CombiProbe 2. With the whisker’s transceivers located close to the target, it provides the firmest signal stability at the highest transfer speeds. Each of our whisker models is optimized to perfectly match the physical and electrical specification of the target's debug and trace ports.
Two multipurpose connectors enable your CombiProbe 2 to operate two Whiskers at once. Your CombiProbe 2 can debug and trace two completely separate target SoCs at the same time while allowing you to observe the precise timing of events within and between both SoCs.
Moreover, one multipurpose connector can be equipped with our optional Mixed-Signal Probe, enriching the trace analysis with time-correlated external analog and digital signals, enabling energy profiling, communication bus decoding, voltage fluctuation detection, and more.
Maximize Bandwidth with AutoFocus Technology
To connect your target’s debug/trace port to the CombiProbe, you need a whisker, which exists in several variants for different needs.
The most popular variants are the MIPI20T-HS and MIPI34 whisker. Both support our AutoFocus technology, which automatically adjusts the sampling point for each signal of your trace lines. This results in more reliable trace capture, with less concern about board routing, impedance, and length matching.Know the AutoFocus technology
Configuration Examples for CombiProbe 2
Debug and Trace of Dual-Chip Arm Cortex-M Processors
Safety critical applications often use two redundant processors making identical calculations. If the two separate embedded systems do not reach a consensus, the applications have to fall back to a safe state. A CombiProbe 2 with two Whiskers lets you develop this system by allowing you to record the dynamic behavior of both control units, timestamp the events with the same clock, and thus allow you to precisely follow the interaction between both units.
Analyze Automotive SoCs with AUTOSAR Adaptive Platform
Profile your AUTOSAR Adaptive Platform using the System Trace Microcell (STM). Arm SoCs can emit high-level messages created by the target’s software stack. Lauterbach provides an ARTI kernel driver which provides you with information about your AUTOSAR Adaptive Applications and their states by using the STM messages captured by the CombiProbe 2.
Using a Mixed-Signal Probe, you may capture any related external events e.g. CAN frames.
Debug Intel® CPUs
The MIPI60-Cv2 Whisker for our CombiProbe 2 was specially designed to support the Intel® Debug Port Specification. Thus, this configuration includes hook pins for special functions (e.g. stall execution during reset sequence), can receive PMODE packages, and has extra survivability features to manually control threshold voltages and slew rates. Furthermore, two independent JTAG chains and system trace are supported.
Benefit from RISC-V Compact Trace
While you can debug any RISC-V core with a CombiProbe 2, its real power is unleashed with SoCs containing RISC-V cores from SiFive. These cores often implement a Nexus trace with a 4-bit Pin Interface Block (PIB) off-chip trace interface, which allows you to record the program flow over time for profiling your code performance or to find tricky bugs which only appear in real time. Your CombiProbe 2 will support the upcoming N-Trace Specification once it is ratified by the RISC-V Foundation.
The Mixed-Signal Probe can record your system's power consumption and correlate it with the program flow to pinpoint power-hungry code sections.
Maximum Performance for All Debug Protocols
JTAG (IEEE 1149.1)
JTAG is the communication protocol commonly available on most CPUs. Originally developed for Boundary Scan device testing, JTAG allows an external tool to communicate with a Test Access Point (TAP) controller inside a chip. A TAP is the connection to the debug infrastructure within a chip. TAPs can be chained to allow debugging of several cores via a single debug probe.
cJTAG (IEEE 1149.7)
Compact JTAG (cJTAG) is a technology based on JTAG which reduces the pin count of the debug interface by serializing the JTAG communication between the debugger and the core’s Test Access Points (TAPs). Multiple chips can be supported in a star topology. Compared to normal JTAG, it saves costs for physical pins with a slightly reduced debug performance.
CoreSight Serial Wire Debug (SWD)
SWD (Serial Wire Debug) is a 2-pin debug interface, defined by Arm® and optimized to access the CoreSight™ debug infrastructure with maximum performance.
The Infineon Device Access Port (DAP) is a versatile debug interface with two or more pins. Its CRC6 protection makes it robust for noisy environments. It supports much higher frequencies than JTAG and also allows transmitting real time trace data with low-to-medium bandwidth.
Compact Trace for Ambitious Developers
Cortex-M ETM and ITM
The Embedded Trace Macrocell (ETM) provides real-time trace information of the program flow and data accesses. Many Cortex-M processors include a 4-bit ETM combined with a CoreSight Instrumenta-tion Trace Macrocell (ITM), allowing our CombiProbe 2 to capture program and data trace along with OS and application events.
Nexus trace (or IEEE-ISTO 5001) is a fairly ubiquitous embedded debug and trace protocol used by many CPU vendors, providing real-time traces of the program flow and data accesses. Some RISC-V devices support Nexus trace features that are compressed in a manner suitable for capture by the CombiProbe 2.
TriCore Compact Function Trace
On many TriCore processors, the Compact Function Trace (CFT) provides data about function entry and exit points. This data can be continuously streamed via an Infineon DAP to the CombiProbe. Additionally, it is possible to gather profiling information of an AUTOSAR Classic operating system.
MIPI System Trace
The System Trace Protocol (STP) is designed to analyze the dynamic behavior of a real-time application on a high level. System trace messages are mostly generated by instrumentation functions in the application code running on the CPU. For profiling the AUTOSAR Adaptive Platform, Lauterbach provides a suitable instrumentation module.
Sets featuring the CombiProbe
Debug cable and 512 MByte of trace memory Bandwidth of 400 MBit/s per trace channel requires at least one of the following A-licenses: LA-3743A Debug. for Cortex-A/R (Armv8 and Armv9) Add. LA-7844A Debug Cortex-M (Armv6/7/8 32-bit) Add. LA-7843A Debug Cortex-A/-R (Armv7 32-bit) Add. LA-7765A JTAG Debugger License for Arm11 Add. LA-7742A JTAG Debugger License for Arm9 Add. LA-7746A JTAG Debugger License for Arm7 Add. LA-2540A Debugger for RISC-V 32-bit Add. LA-2541A Debugger for RISC-V 64-bit Add. Supports the following trace licenses: LA-7970X Trace License for the Arm Architecture LA-2767X Trace License for RISC-V (Debug Cable/COB) requires Power Debug Interface USB 3.0, Power Debug II, PowerDebug PRO, PowerDebug E40 or PowerDebug X50
Debug cable and 512-MByte of trace memory support for DAP Streaming Supports - DAP (DAP2, DAP3, DAPWide, DAP4): up to 160 MHz, 3.3 V or 5.0 V - JTAG: 1.8-5.0 V, up to 60 MHz - DXCPL DAP streaming requires a DAP mode. For performance reasons, we recommend DAPWide at 160 MHz. 26-pin Automotive Connector requires the following A-license: LA-7756A (Debugger for TriCore Standard Additional) trace analysis and display requires LA-3799X (Trace License for TriCore ED) requires Power Debug Interface USB 3.0, Power Debug II, PowerDebug PRO, PowerDebug E40 or PowerDebug X50
Debug cable and 512 MByte of trace memory Bandwidth of 200 MBit/s per trace channel requires at least one of the following A-licenses: LA-3743A Debug. for Cortex-A/R (Armv8 and Armv9) Add. LA-7844A Debug Cortex-M (Armv6/7/8 32-bit) Add. LA-7843A Debug Cortex-A/-R (Armv7 32-bit) Add. LA-7765A JTAG Debugger License for Arm11 Add. LA-7742A JTAG Debugger License for Arm9 Add. LA-7746A JTAG Debugger License for Arm7 Add. Supports the following trace licenses: LA-7970X Trace License for the Arm Architecture requires Power Debug Interface USB 3.0, Power Debug II, PowerDebug PRO, PowerDebug E40 or PowerDebug X50
Debug cable and 512-MByte of trace memory requires the following A-license: LA-7760A (JTAG Debugger for MIPS32) 4-Bit IFlow program trace requires: LA-7971X (Trace License for the MIPS32) requires Power Debug Interface USB 3.0, Power Debug II, PowerDebug PRO, PowerDebug E40 or PowerDebug X50 and TRACE32 software r142224(DVD 2022/02) or newer 5V tolerant inputs; max. output level 3.3V
Digital/Analog probe with 40-pin connector for LA-3204 MicroTrace for Cortex-M (PACK) LA-3080 CombiProbe 2 for MIPI20T-HS (PACK) LA-3082 CombiProbe 2 for MIPS32+4-Bit IFLOW (PACK) LA-3083 CombiProbe 2 for MIPI34 (PACK) LA-2520 / LA-2521 PowerTrace III LA-3121 / LA-3122 PowerTrace Serial 2 Characteristics of digital probe 12 channels (12 data) 0..5 V Input 200 MSamples per channel Characteristics of analog probe 6 Channels -12V..+12V 13 bit resolution, 2 current sense channels, Conversion rate 1 MSample/s Requires TRACE32 software DVD 2021/02 or newer. Recommended accessories: LA-6470 Clip Set (Cable and Clips)