BEAVERTON, USA: Open Core Protocol International Partnership (OCP-IP) announced that the latest comprehensive set of Functional Checks and Assertions is available now to Sponsor-Level Members.
Compliance checks eliminate the need for “best-guess” verification by engineers, making certain an OCP interface complies with the specification, assuring verification quality and that IP blocks are compatible at the system level. This current set of checks supports OCP 3.0 and is now being extended for the next release of OCP, already in advanced stages of development.
These checks define a set of rules for the OCP Specification. Constraints can be as simple as "check that a signal is never X" or may be complex temporal expressions. If no check is violated by functional and/or formal verification, the logic is proven compliant with the protocol.
The compliance checks can be used in several different ways. Formal tools can use checks to be sure a design never violates them, proving OCP compliance. They can also use the same checks to cover the number of times a given restraint was hit. Functional verification tools can use the properties to build protocol checkers (in System Verilog/VHDL/e/SystemC, etc.). By applying stimuli to the design under test (DUT) and verifying that protocol checkers are not reporting violations, OCP compliance is verified.
“OCP-IP is committed to providing a complete infrastructure surrounding the OCP Specification which allows our members to quickly begin using OCP," said Ian Mackintosh, president and chairman, OCP-IP. “In addition to our own CoreCreator (including OCP checker), OCP Tracker, and OCP Conductor verification tools, and documented checks, there is a large range of products available from commercial providers. These tools eliminate the need for 'best-guess' verification by engineers.”