The Open Core Protocol (OCP) is an openly licensed, core-centric protocol intended to meet contemporary system level integration challenges. OCP defines a bus-independent, configurable and scalable interface for on-chip subsystem communications. OCP International Partnership (OCP-IP) now offers the 2.2 version specification that further extends capabilities in areas such as very high performance multithreading, synchronization primitives and single-request/multiple-data transactions. OCP data transfer models range from simple request-grant handshaking through pipelined request-response to complex out-of-order operations.
Legacy IP cores can be adapted to OCP, while new implementations may take full advantage of advanced features: designers select only those features and signals encompassing a core’s specific data, control and test configuration. Core definition using OCP encapsulates a complete system integration description enabling core and test bench reuse without rework. Not only does OCP provide clear delineation of design responsibilities for core authors and System-on-Chip (SoC) integrators, but also institutes a key partitioning formalism for verification engineers and automation software.
The aim of the members is to establish a de facto standard which is widely supported by the industry
Read more about Open Core Protocol: Advantages, Disadvantages, Highlights
Famous quotes containing the words open and/or core:
“Listen to me, as if I were Sybaris barking with all his heads, at the gates of Hell, I will tell you where to take it. But don’t ... don’t open the box!”
—A.I. (Albert Isaac)
“It is possible to have a strong self-love without any self-satisfaction, rather with a self-discontent which is the more intense because one’s own little core of egoistic sensibility is a supreme care.”
—George Eliot [Mary Ann (or Marian)