Jump to content

BEGIN_REQ/END_REQ and BEGIN_RESP/END_RESP mark time points in the protocol.


Recommended Posts

1602143040_Screenshotfrom2019-01-1615_28_08.png.ff2e02063cbed5ff22c44ee8f726eeb5.png

 

Hi,

above image is taken from LRM from section 11.1.2.10,  

During read command

1.is it 10ns in return path is for the target to perform read from  target memory  to data_pointer of initiator present in target as a part of generic payload member?  if not than when is the actual read happens ?

2.what is target doing from 110ns to 150ns ?

3.how do i interpret 5ns present in return of BEGIN_RESP

Please help . 

 
Link to comment
Share on other sites

The 10ns tells the initiator that the request phase (or address phase in some bus protocols) takes 10ns.

During 110ns and 150ns simulation time the target executes the read.

The 5ns in the BEGIN_RESP/END_RESP tells the target that the data/status transfer over the bus (the data phase on some bus protocols) takes 5ns.

The annotated times in the return path is to save a second function call (END_REQ and END_RESP respectively) at two more simulation time points (120ns and 155ns). This way you can increase the performance of the simulation.

Best regards

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...