Ocp profiles discussion input p klapproth philips semiconductors 17 06 2004
Download
1 / 7

OCP Profiles Discussion Input P. Klapproth Philips Semiconductors 17.06.2004 - PowerPoint PPT Presentation


  • 65 Views
  • Uploaded on

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)

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about ' OCP Profiles Discussion Input P. Klapproth Philips Semiconductors 17.06.2004' - zuwena


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.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
Ocp profiles discussion input p klapproth philips semiconductors 17 06 2004

OCP ProfilesDiscussion InputP. Klapproth Philips Semiconductors17.06.2004


Address mapped block data flow profile
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


Addressed mapped block data flow profile
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


Address mapped streaming data flow profile
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


Addressed mapped streaming data flow profile
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}


Peer to peer streaming data flow profile
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


Peer to peer streaming data flow profile1
Peer-to-Peer Streaming Data Flow Profile

MCmd

Master

Slave

MCmd

SCmdAccept

Mdata

SData

SResp

MRespAccept


ad