Defining standard Debug Interface Socket requirements for OCP-compliant multicore SoCs: Part 2
By Neal Stollon, HDL Dynamics, Bob Uvacek, Pixelworks, and Gilbert Laurenti, Texas Instruments
Jul 16 2007 (0:05 AM), Embedded.com
Jul 16 2007 (0:05 AM), Embedded.com
As discussed in Part 1 in this series, in the same way the OCP data socket is a superset for the different bus interfaces and data structures, an OCP debug socket will provide a superset of the debug solutions based on standardized libraries of debug IP blocks that interact with the debug sockets signals. This allows the following:
-
Signal level observation (bus and system trace) and control (triggering)
-
Consistent (multiple) processor software debugger and bus traffic observation interfaces
-
Special debug features for security islands, voltage islands, gated clock islands etc.
-
New classes of debug errors (which are different from system errors.
To read the full article, click here
Related Semiconductor IP
- UCIe Chiplet PHY & Controller
- MIPI D-PHY1.2 CSI/DSI TX and RX
- Low-Power ISP
- eMMC/SD/SDIO Combo IP
- DP/eDP
Related White Papers
- Defining standard Debug Interface Socket requirements for OCP-Compliant multicore SoCs: Part 1
- Standard Debug Interface Socket Requirements For OCP-Compliant SoC
- Standard socket interface tapped
- Multicore SoCs change interconnect requirements
Latest White Papers
- Achieving Lower Power, Better Performance, And Optimized Wire Length In Advanced SoC Designs
- The pivotal role power management IP plays in chip design
- What tamper detection IP brings to SoC designs
- Analyzing Modern NVIDIA GPU cores
- RISC-V in 2025: Progress, Challenges,and What’s Next for Automotive & OpenHardware