Skip to content

1.4.1 Block Diagram

[Figure 12: Block Diagram — image not included]

Table 15: TC39xED Components

ComponentDefinition
AGBTAurora GigaBit Trace module on EEC
BBBBack Bone Bus with FPI protocol
BOBBus Observation Block. Trace and trigger logic within MCDS
CerberusCentral debug and tool access control unit is part of OCDS
DAPDevice Access Port. Fast and robust 2/3 pin tool interface (15/30 MB/s).
DAPEIndependent DAP instance for connecting a second tool to the ED
DMADirect Memory Access controller. Shares SRI/SPB bus interfaces with Cerberus.
EDEmulation Device for calibration, measurement and debug
EECEmulation Extension Chip part
EMEMExtension Memory (calibration and trace memory)
FPIFlexible Peripheral Interconnect, the protocol of SPB and BBB buses
IOC32P/EIO Client for accessing BBB by DAP/DAPE
MCDSMulti-Core Debug Solution
OCDSOn-Chip Debug Support
OTGBOCDS Trigger Bus: collects interrupt and peripheral trace and trigger signals.
POBProcessor Observation Block
SBCUSPB Bus Control Unit
SoCSystem on Chip (used also for “product chip part”)
SPBSystem Peripheral Bus with FPI protocol
SRIShared Resource Interconnect cross bar
TMUXTrace Multiplexer

The Extension Memory (EMEM) as part of the EEC is used for two conceptually different purposes: trace buffering and overlay memory.

Trace buffering is a non-intrusive tool to aid the debugging process. Matching elements from the MCDS module are provided to translate captured signals into trace messages. These messages are buffered in EMEM and can then be read by the tool.

Overlay memory allows RAM partitions to be mapped into the address ranges of the CPUs, optionally replacing parts of the TC3xx’s local Flash.