Extend XCP probe debugging with an Active Probe for full Aurora Gigabit Trace
In this topic:
Quick start
Combine an XCP probe with an iC7max BlueBox and an Infineon Active Probe to get full debug and high-bandwidth trace in a single session:
1. Connect the hardware: BlueBox + Active Probe to the trace connector, XCP probe to the debug connector
2. Configure winIDEA for BlueBox with Active Probe as the primary debug/trace device
3. Set XCP as the debug mode and point winIDEA to the XCP probe's IP and port
4. Power on in order: BlueBox, then XCP probe, then the target
You have a live debug and trace session. The Analyzer receives full Aurora Gigabit Trace data while the XCP probe handles target debugging.
Overview
The XCP probe used through the Debug over XCP Master function gives you target debugging and only limited trace. This guide shows how to remove that limitation by adding an iC7max BlueBox with an Infineon Active Probe to the same target. The Active Probe connects to the trace connector and uses the full bandwidth of the Aurora Gigabit Trace interface, while the XCP probe continues to handle debug.
Use this setup when
•You need full trace bandwidth alongside XCP-based debugging
•Your target exposes separate debug and trace connectors
•You are working with an Infineon AURIX that supports Aurora Gigabit Trace
Before you start
Hardware requirements
•iC7max BlueBox
•Infineon SGBT or Infineon AGBT Active Probe (no other Active Probe models are supported)
•XCP probe
•Target board with separate debug and trace connectors
Software requirements
•winIDEA with a license that covers BlueBox and Analyzer
Network requirements
•BlueBox connects to the host PC and to the XCP probe over Ethernet
•Your network must allow traffic between BlueBox and the XCP probe (check firewall rules and subnet settings if they are on different segments)
|
The trace connector on the target must carry only trace signals. Debug signals are driven by the XCP probe. Do not wire debug signals to the Active Probe connector. Doing so can damage both devices. |
Steps
Step 1: Connect the hardware
1. Connect BlueBox and the Active Probe to the target's trace connector.
2. Connect the XCP probe to the target's debug connector.
3. Connect BlueBox to your network over Ethernet.
The two probes divide responsibilities at the hardware level. The Active Probe owns the trace interface; the XCP probe owns the debug interface. Mixing signals between the two connectors can damage the hardware.
Step 2: Configure winIDEA for BlueBox with Active Probe
1. Open winIDEA and create a new winIDEA workspace.
2. Configure the hardware as you would for a normal BlueBox + Active Probe debug/trace session.
3. Select iC7max BlueBox as the debug device and choose your Active Probe model (Infineon AGBT or SGBT).
winIDEA shows BlueBox and the Active Probe as the active hardware. You have not yet connected to the target.
Step 3: Configure XCP
BlueBox needs the XCP probe's network address to forward debug traffic to it. Without this, winIDEA cannot reach the XCP probe.
1. Select Hardware > SoC Options... > SoC and set Debug Mode to XCP.
2. Go to Hardware > SoC Options... > XCP and enter the Port and Server IP of your XCP probe.
Step 4: Power on the devices in order
BlueBox and the XCP probe must be ready before the target starts. Powering the target first can cause the probes to miss the boot sequence or fail to attach.
Power on in this sequence:
1. BlueBox
2. XCP probe
3. Target
All three devices are powered and ready.
Step 5: Start your debug and trace session
Use winIDEA's Debug and Analyzer views as you would in any normal debug/trace session. Set breakpoints, step through code, and capture trace data.
Troubleshooting
winIDEA cannot connect to the XCP probe
BlueBox cannot reach the XCP probe over the network.
Fix:
1. Confirm the XCP probe is powered on and connected to the same network as BlueBox.
2. Verify the IP address and port in Hardware > SoC Options... > XCP match the XCP probe's actual settings.
3. Check that your firewall or switch is not blocking traffic between BlueBox and the XCP probe.
4. If BlueBox and the XCP probe are on different subnets, confirm routing is in place.
If that doesn't work:
•Try connecting BlueBox and the XCP probe directly with a crossover cable or through an unmanaged switch to rule out network policy issues
•Check the XCP probe's own configuration tool to confirm its IP settings
Trace data is missing or the Analyzer shows no data
The Active Probe may not be receiving trace signals.
Fix:
1. Confirm the Active Probe is connected to the trace connector.
2. Verify the trace connector on the target carries only trace signals (no debug signals wired in).
3. Check that the Active Probe model is SGBT or AGBT; other models are not supported in this setup.
If that doesn't work:
•Confirm the target's trace interface is enabled in its SoC configuration.
•Check the Active Probe's status LEDs for any fault indication.
The target behaves unexpectedly or the probe reports a hardware fault
Debug signals may have been connected to the Active Probe's trace connector.
Fix:
1. Power off all devices immediately
2. Inspect the trace connector wiring on the target — remove any debug signals from it
3. Check both probes for physical damage before powering on again
See also
•iC7max BlueBox - Hardware User Manual
•Infineon SGBT Active Probe - Hardware User Manual
•Infineon AGBT Active Probe - Hardware User Manual
