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

More documents

Recommendations

Info

OCP-IP Confidential • The “OCP System monitoring” debug component shall allow monitoring the “OCP System” bus traffic o Focus on specific OCP transactions o User defined transactions filtering o Initiator, thread, address range, DMA logical channel • An emulator shall be able to configure the “OCP System monitoring” component from the external [JTAG] interface through the “OCP Debug” bus. The “OCP System monitoring” component shall have options to allow: • Align the OCP transactions requests & responses • Capture additional OCP transactions qualifiers • Export the captured traffic data through the “OCP Debug” to a “Trace Export” component • Support continuous System monitoring • Preserve the OCP System bus behavior • Be security aware The “Trace Export” component shall: • Implement an elastic buffer • Optionally build trace packets for different (MIPI/Nexus) protocols. • Support a trace export bandwidth compatible with OCP System traffic peaks • Allow SW instrumentation interleaving The “Trace Buffer” component shall: • Provide flexibility to disable capture around a trigger • Allow system trace data reads o From the JTAG-OCP component o From the application SW • Allow interleaving several trace flows • Allow multi-threaded data observation 4. Extended (Optional) Debug interfaces Extended debug signals support application specific or optional functionality designed into the target system (Power Islands, Secure subsystems, others) or into the debug subsystem (Performance Monitoring, Timestamps, others). The extended signals support special functionality designed into the target system. In the OCP based case they follow the point-topoint communication protocol and expose the OCP signaling to the debugger. RunControl allows a clock synchronized program execution of two cores that would run asynchronously in normal case. That makes it possible to time align the instruction streams to study interdependency. This is a simplified method to avoid the hardware for time stamping. 20 of 62 © 2007 OCP-IP Association, All Rights Reserved.
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.
Page 1 and 2: OCP-IP Confidential Open Core Proto
Page 3 and 4: OCP-IP Confidential Table of Conten
Page 5 and 6: OCP-IP Confidential 1. OCP Debug sp
Page 7 and 8: OCP-IP Confidential 1.2 OCP Debug s
Page 9 and 10: OCP-IP Confidential to facilitate d
Page 11 and 12: OCP-IP Confidential 2.2 Technical s
Page 13 and 14: OCP-IP Confidential does place limi
Page 15 and 16: OCP-IP Confidential Control signals
Page 17 and 18: OCP-IP Confidential Cross-Trigger L
Page 19: OCP-IP Confidential in target trigg
Page 23 and 24: OCP-IP Confidential tracing is acti
Page 25 and 26: OCP-IP Confidential Restarting core
Page 27 and 28: OCP-IP Confidential Appendix Implem
Page 29 and 30: OCP-IP Confidential - Indirect Bran
Page 31 and 32: OCP-IP Confidential Note that the s
Page 33 and 34: OCP-IP Confidential Example 2. Wire
Page 35 and 36: OCP-IP Confidential A.2.1 OCP Debug
Page 37 and 38: OCP-IP Confidential concurrent with
Page 39 and 40: OCP-IP Confidential • Suspend fun
Page 41 and 42: OCP-IP Confidential A.4.1.5 BCU OCD
Page 43 and 44: OCP-IP Confidential Figure A.4 Brea
Page 45 and 46: OCP-IP Confidential OCP- MCDS Wrapp
Page 47 and 48: OCP-IP Confidential Bit Field Width
Page 49 and 50: OCP-IP Confidential B.3.1 EMUx Trig
Page 51 and 52: OCP-IP Confidential If EMU1 is driv
Page 53 and 54: OCP-IP Confidential exist, C-TRIG w
Page 55 and 56: OCP-IP Confidential number. This wi
Page 57 and 58: OCP-IP Confidential Debug & Analysi
Page 59 and 60: OCP-IP Confidential C.2 Nexus Messa
Page 61 and 62: OCP-IP Confidential resources to he

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

Create successful ePaper yourself

Delete template?

Save as template?