09.11.2014 Views

CoreSight SoC Technical Reference Manual - ARM Information Center

CoreSight SoC Technical Reference Manual - ARM Information Center

CoreSight SoC Technical Reference Manual - ARM Information Center

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Functional Overview<br />

2.4 Trigger components<br />

<strong>CoreSight</strong> <strong>SoC</strong> contains the following trigger components to control the logging of debug<br />

information:<br />

• Cross Trigger Interface.<br />

• Cross Trigger Matrix.<br />

The Cross Trigger Interface (CTI) and Cross Trigger Matrix (CTM) form the Embedded Cross<br />

Trigger (ECT) sub-system that enables the <strong>ARM</strong> Embedded Trace Macrocell (ETM)<br />

subsystems to interact, that is cross trigger, with each other. The main function of the ECT is to<br />

pass debug events from one processor to another. For example, the ECT can communicate<br />

debug state information from one processor to the others, so that you can stop the program<br />

execution on one or more processors at the same time if required.<br />

2.4.1 Cross Trigger Interface<br />

The CTI combines and maps the trigger requests, and broadcasts them to all other interfaces on<br />

the ECT sub-system. When the CTI receives a trigger request it maps this onto a trigger output.<br />

This enables the ETM subsystems to cross trigger with each other. Figure 2-25 shows the<br />

external connections on the CTI.<br />

Block clock<br />

and<br />

reset<br />

APB clock<br />

and<br />

reset<br />

cticlk<br />

cticlken<br />

ctiresetn<br />

pclkdbg<br />

pclkendbg<br />

presetdbgn<br />

tisbypassin<br />

tisbypassack<br />

ctitrigin[7:0]<br />

ctitrigoutack[7:0]<br />

ctitrigout[7:0]<br />

ctitriginack[7:0]<br />

CTM<br />

link<br />

Trigger<br />

interface<br />

General<br />

control<br />

Sync<br />

by-pass<br />

control<br />

Handshake<br />

bypass<br />

Debug<br />

enable<br />

masking<br />

se<br />

ctiapbsbypass<br />

cisbypass<br />

asicctl[7:0]<br />

ctiapbsbypass[7:0]<br />

cisbypass[3:0]<br />

cihsbypass[3:0]<br />

tihsbypass[7:0]<br />

tinidensel[7:0]<br />

todbgensel[7:0]<br />

Cross Trigger<br />

Interface (CTI)<br />

ctichin[3:0]<br />

ctichoutack[3:0]<br />

ctichout[3:0]<br />

ctichinack[3:0]<br />

paddrdbg[11:2]<br />

pwritedbg<br />

pwdatadbg[31:0]<br />

pseldbg<br />

penabledbg<br />

pclkendbg<br />

paddrdbg31<br />

prdatadbg[31:0]<br />

preadydbg<br />

Channel<br />

interface<br />

Optional<br />

APB<br />

port<br />

Figure 2-25 Cross Trigger Interface block diagram<br />

2.4.2 Cross Trigger Matrix<br />

The CTM block controls the distribution of trigger requests. It connects to at least two CTIs and<br />

to other CTMs where required in a design. Figure 2-26 on page 2-19 shows the external<br />

connections on the CTM block.<br />

You must configure the CTM with the following parameter that defines the width of some ports<br />

of the block:<br />

• ECTCHANNELWIDTH. See CW in Figure 2-26 on page 2-19 where CW=ECTCHANNELWIDTH-1.<br />

<strong>ARM</strong> DDI 0480D Copyright © 2011, 2012 <strong>ARM</strong>. All rights reserved. 2-18<br />

ID010213<br />

Non-Confidential

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!