Forum Discussion
Occasional ContributorCreating a AXI master interface for New Platform component
What you've attached are just changes to the standard AXI behaviors, not specific signal roles. As you've found with the Component Editor, you must have certain signals and some at matching bus widths to follow the protocol for it to work as a custom component with an AXI interface.
Use the template to add all the signals in to your design and work from there. Platform Designer will only work with the true standard interface and the normal way that the signals are supposed to work, so "AXI-like" behavior wouldn't work unless you customize your component's logic to work with this (instead of relying on the interconnect to do it for you).
You say you're not familiar enough with AXI, but from looking at this, I think you may need get more information about the standard for yourself to make this work.
Super ContributorThe errors are pretty self-explanatory, aren't they? Bit widths and missing signals.
I don't know how you're setting up the signals and interfaces (from existing HDL code or manually), but if you select a template from the Templates menu there at the top of the Component Editor, you're guaranteed to have all the signals you need.
If you have existing HDL code, you would then need to add the code to the component on the Files tab, analyze the HDL files there as well, and then map the ports in the code to interfaces and signals on that tab.
Qazi_ShahidActually, I am trying to port NVDLA Architecture on FPGA. NVDLA has implemented an AXI like master interface to communicate with DRAM directly.
By "AXI like" I mean that few signals of AXI protocol are not implemented in and explanation for that is given in the nvdla_axi_assumptions.png file attached below. I don't have enough knowledge about AXI-protocol to understand the assumption given in the .png file.
@sstrell Could please go through the nvdla_axi_assumptions.png file and guide me on how to declare the logic for missing signals based on the information given in the file.
- sstrell
What you've attached are just changes to the standard AXI behaviors, not specific signal roles. As you've found with the Component Editor, you must have certain signals and some at matching bus widths to follow the protocol for it to work as a custom component with an AXI interface.
Use the template to add all the signals in to your design and work from there. Platform Designer will only work with the true standard interface and the normal way that the signals are supposed to work, so "AXI-like" behavior wouldn't work unless you customize your component's logic to work with this (instead of relying on the interconnect to do it for you).
You say you're not familiar enough with AXI, but from looking at this, I think you may need get more information about the standard for yourself to make this work.
