OCP Comliance Checks_101905 - OCP-IP
OCP Comliance Checks_101905 - OCP-IP
OCP Comliance Checks_101905 - OCP-IP
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
Compliance <strong>Checks</strong> Details 413.3.2 request_hold_NomenclatureProtocol version 2.0Protocol hierarchySignal groupCritical signalsRequestDataflowMAddr, MCmd, MData, MAddrSpace, MByteEn, MDataInfo,MReqInfo, MAtomicLength, MBurstLength, MBurstPrecise,MBurstSeq, MBurstSingleReq, MReqLast, MConnID,MThreadIDAssertion typeHoldDescriptionOnce a request phase has begun, the following signals may not change their value until the<strong>OCP</strong> slave has accepted the request.Basic SignalsMAddrMCmdMDataSimple ExtensionsMAddrSpaceMByteEnMDataInfoMReqInfoBurst ExtensionsMAtomicLengthMBurstLengthMBurstPreciseMBurstSeqMBurstSingleReqMReqLastThread ExtensionsMConnIDMThreadIDThe following exception applies: If datahandshake=1 and mdatabyteen=1 then MByteEn canchange for write accesses during the request phase.<strong>OCP</strong>-<strong>IP</strong> Confidential