- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
In the PCI Express Megafunction, two options are provided for the interface between ip core and application:
Descriptor/Data and Avalon-ST, and the latter is recommended by Altera in the User's Guide. However, as I read through the VHDL code of the chaining dma example using Avalon-ST, I found that, we first interface with ip core using A-ST, and then we use a module to change the A-ST to Descriptor/Data. The datapath is : core --> core to A-ST --> A-ST to D/D --> App And if we use D/D instead, the datapath is: core --> core to D/D --> App From the app layer's perspective, both options provides the same interface. So why not use D/D directly and bother to use A-ST ? Is there any advantage we can make from the Avalon-ST?Link Copied
3 Replies
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
still no reply..
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I kind of wondered the same thing. I know there was honestly a good reason i thought as to why i chose the avalone interface with the D/D adapter, but that was a few years ago for me and can't quite remember. I have been anxious to see if anyone else knew.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
It sounds like it was the fastest way to re-use the existing Desc/Data chaining DMA design.

Reply
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page