Open Core Protocol Debug Interface Specification rev 1.0 - OCP-IP

OCP-IP Confidential
Security concepts require enabling debug of sensitive locations only during chip validation and
disabling it in the production chips. OCP security signaling is here extended to the debug
socket so debug IP blocks can implement such concepts.
Modern deep submicron processes overheat easily so power management by switching off
clock and even switching off power supply to certain IP blocks is very popular. Debugger shall
not get locked or interrupted when dealing with such IP blocks if addressed accidentally in a
debug session. Power-management debug signals help to avoid any confusion.
Performance monitoring enables observation of selected threads, initiators, and targets to
identify data traffic and measure data bandwidth. In all cases, they follow the point-to-point
communication protocol and expose the OCP signaling to the debugger via a JTAG controlled
or memory mapped registers.
4.1 Performance Monitoring
Performance monitoring enables observation of selected threads, initiators, and targets to
identify data traffic and measure data bandwidth.
Table 4.1 OCP Debug Performance Monitoring Interface Socket
Performance
monitoring Description Comment
MConnID
MChannelID
MReqWatch[x]
PMSampling
Identifies the initiator.
Routed to target
Identifies the DMA channel
initiator. Routed to target
Qualifies an OCP request
Periodic performance metrics
sampling
OCP Performance Monitoring – General Configuration
MThread-ID shall not be used to track cycles
consumed by a specific initiator
MThread-ID shall not be used to track cycles
consumed by a specific DMA channel
initiator
for which subsystem has detected a
watchpoint hit
Initiates a transfer of the performance
metrics computed by the system interconnect
to the trace export component. Periodic
sampling strobe can potentially be generated
within the OCP fabric.
• A built-in OCP debug component shall allow monitoring the OCP System bus bandwidth.
• An emulator shall be able to configure the “OCP Performance monitoring” component
from the external [JTAG] interface through the “OCP Debug” bus.
• OCP Initiator's transactions to be monitored for a specific OCP target
• Monitoring window [Start & Stop triggers]
• System event latency
The “OCP Performance monitoring” component shall:
21 of 62
© 2007 OCP-IP Association, All Rights Reserved.