OCP Specification 3.1 - OCP-IP

Overview 3DRAFTanalysis and reduce implementation area. Support for this wide range ofbehavior is possible through the use of synchronous handshaking signalsthat allow both the master and slave to control when signals are allowed tochange.1.2 Compliance1. The core must include at least one OCP interface.2. The core and OCP interfaces must be described using the coreconfiguration files described in Chapter 7 on page 131. (RTL configurationfiles are deprecated.)3. Each OCP interface on the core must:• Comply with all aspects of the OCP interface specification• Have its timing described using a synthesis configuration file followingthe syntax specified in Chapter 10 on page 155.4. The following practices are recommended but not required:a. Each non-OCP interface on the core should:• Be described using the core configuration files described inChapter 7 on page 131• Have its timing described using a synthesis configuration file withthe syntax specified in Chapter 10 on page 155.b. A performance report as specified in Chapter 17 on page 363 (or anequivalent report) should be included for the core.OCP-IP Confidential May 14, 2012