Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

how did the address such as "uuid_11aa22bb_cac7_459a_a759_2eab2efd02ae" in axi_mem_if_SP.xml come from? #2

Closed
brandot4life opened this issue Nov 13, 2023 · 7 comments

Comments

@brandot4life
Copy link

As title,
I'd really like to know how did the value and parameterId come from? Is there any meaning for it?
Thanks in advance

BRs

@epekkar
Copy link
Collaborator

epekkar commented Nov 13, 2023

Hi,

uuid_11aa22bb_cac7_459a_a759_2eab2efd02ae is a Universally Unique Identifier for the parameter AXI4_ADDRESS_WIDTH. When used in an expression within the component axi_mem_if_SP, it evaluates to the value of the parameter (32 by default).

@epekkar epekkar closed this as completed Nov 13, 2023
@brandot4life
Copy link
Author

brandot4life commented Nov 13, 2023 via email

@epekkar
Copy link
Collaborator

epekkar commented Nov 13, 2023

The IP-XACT standard requires that parameters within a component have unique ids for unambiguity. The means of selecting the ids is not restricted in any ways i.e. you could use whatever ids as long as there are no duplicates. The XML files in this repository are created with the Kactus2 tool which automatically generates UUIDs for parameters.

@brandot4life
Copy link
Author

brandot4life commented Nov 13, 2023 via email

@epekkar
Copy link
Collaborator

epekkar commented Nov 13, 2023

That is to ensure the same value for the (component) parameter which controls e.g. port widths and the module parameter which adds details for RTL .

@brandot4life
Copy link
Author

brandot4life commented Nov 13, 2023 via email

@epekkar
Copy link
Collaborator

epekkar commented Nov 14, 2023

That is mostly to save time on creating the IP-XACT files. The objective in this project was to create a meaningful set of IP-XACT files from the top down. So most of the omitted RTL files are either low in the hierarchy or not that important for the structural description of the system.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants