Hard Processor System Technical Reference Manual: Agilex™ 5 SoCs

ID 814346
Date 7/19/2024
Public

A newer version of this document is available. Customers should click here to go to the newest version.

Document Table of Contents

15.6.3. Configuring Embedded Cross-Trigger Connections

CTI interfaces are programmable through a memory-mapped register interface. To access registers in any CoreSight* component through the debugger, the register offsets must be added to the CoreSight* component’s base address. That combined value must then be added to the address at which the ROM table is visible to the debugger (0x80000000).

Each CTI has two interfaces, the trigger interface, and the channel interface. The trigger interface is the interface between the CTI and other components. It has eight trigger signals, which are hardwired to other components. The channel interface is the interface between a CTI and its CTM, with four bidirectional channels. The mapping of trigger interface to channel interface (and vice versa) in a CTI is dynamically configured. You can enable or disable each CTI trigger output and CTI trigger input connection individually.

For example, you can configure trigger input 0 in the FPGA–CTI to route to channel 3 and configure trigger output 3 in the FPGA–CTI and trigger output 7 in CTI–0 in the MPU debug subsystem to route from channel 3. This configuration causes a trigger at trigger input 0 in FPGA–CTI to propagate to trigger output 3 in the FPGA–CTI and trigger output 7 in CTI–0. Propagation can be single-to-single, single-to-multiple, multiple-to-single, and multiple-to-multiple.

There are soft logic signals in the FPGA that are individually connected to trigger inputs in the FPGA–CTI that are configurable.

  • Connected to a trigger input—to trigger a flush of trace data to the TPIU. For example, you can configure channel 0 to trigger output 2 in the CTI. Then configure trigger input T3 to channel 0 in FPGA–CTI. Trace data is flushed to the TPIU when a trigger is received at trigger output 2 in the CTI.
  • Connected to trigger input T2—to trigger a STM message. The CTI output triggers 4 and 5 are wired to the STM CoreSight* component in the HPS. For example, configure channel 1 to trigger output 4 in the CTI; and then configure trigger input T2 to channel 1 in FPGA–CTI.
  • Connected to trigger input T1—to trigger a breakpoint on CPU 1. Trigger output 1 in CTI–1 is wired to the debug request (EDBGRQ) signal of CPU-1. For example, configure channel 2 to trigger output 1 in CTI–1. Then configure trigger input T1 to channel 2 in FPGA–CTI.

For more information about the cross-trigger interface, refer to the CoreSight Technical Reference Manual.

Related Information

CoreSight SoC-600 Technical Reference Manual