1 / 7

OCP Profiles Discussion Input P. Klapproth Philips Semiconductors 17.06.2004

OCP Profiles Discussion Input P. Klapproth Philips Semiconductors 17.06.2004. Address Mapped Block Data Flow Profile. Application: DMA capable IP cores communicating blocks of data Initiator read/write | write-only | read-only interface Features Block type communication (includes 1-element)

zuwena
Download Presentation

OCP Profiles Discussion Input P. Klapproth Philips Semiconductors 17.06.2004

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. OCP ProfilesDiscussion InputP. Klapproth Philips Semiconductors17.06.2004

  2. Address Mapped Block Data Flow Profile • Application: • DMA capable IP cores communicating blocks of data • Initiator read/write | write-only | read-only interface • Features • Block type communication (includes 1-element) • 32 bit address • Natural data width & block size (unconstrained) • Optional use of byte enables • Use of non-posted write preceding producer/consumer synchronization • Single-thread • Does not describe side-band and test extensions

  3. Addressed Mapped Block Data Flow Profile MCmd, Maddr, MBurstLength, (MByteEn) Master Slave MCmd SCmdAccept Mdata, (MDataByteEn) MDataValid SDataAccept SData, SResp SResp MRespAccept MCmd ={ Idle | Write | Write NonPost | Read} MBurstPrecise=1, MBurstSeq=1, MBurstSingleReq=1

  4. Address Mapped Streaming Data Flow Profile • Application: • DMA capable IP cores communicating streams of data • Initiator read/write | write-only | read-only interface • Features • streaming type communication (= an undefined length sequence of data elements at consecutive addresses) • 32 bit address • Merged or separate Command/Write data flow • Natural data width • Optional use of byte enables • Use of non-posted write preceding producer/consumer synchronization • Single-thread • Does not describe side-band and test extensions

  5. Addressed Mapped Streaming Data Flow Profile MCmd, Maddr, (MByteEn) Master Slave MCmd SCmdAccept Mdata, (MDataByteEn) MDataValid SDataAccept SData, SResp SResp MRespAccept MCmd ={ Idle | Write | Write NonPost | Read}

  6. Peer-to-Peer Streaming Data Flow Profile • Application: • IP cores communicating streams of pure data peer-to-peer • Initiator read-only | write-only interface • Features • streaming type communication (= an undefined length sequence of data elements) • Merged Command / write data flow • No address • Natural data width • Implicit consumer/producer synchronization • Single-thread • Does not describe side-band and test extensions

  7. Peer-to-Peer Streaming Data Flow Profile MCmd Master Slave MCmd SCmdAccept Mdata SData SResp MRespAccept

More Related