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
- 1.8V/3.3V I/O Library with 5V ODIO & Analog in TSMC 16nm
- ESD Solutions for Multi-Gigabit SerDes in TSMC 28nm
- High-Speed 3.3V I/O library with 8kV ESD Protection in TSPCo 65nm
- Verification IP for DisplayPort/eDP
- Wirebond Digital and Analog Library in TSMC 65nm
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
- 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
- Leveraging RISC-V as a Unified, Heterogeneous Platform for Next-Gen AI Chips
- Design and implementation of a hardened cryptographic coprocessor for a RISC-V 128-bit core