Jump to content

synchronisation issues with DMI transfer

Recommended Posts

It's called "direct memory interface", because it's a direct access to a target's memory range.  The target has no way to observe accesses from initiators to the currently allowed DMI ranges.  If the target requires to observe such accesses, you should not grant DMI access for these address ranges during the relevant communication states/phases.  Usually, DMI is preferred for the plain memory parts of the target's interface, while (control) registers often require explicit TLM transactions for that reason.



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.

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...