-
Notifications
You must be signed in to change notification settings - Fork 3
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
Comments
Hi,
|
Hi,
So it can be another UUID that we generated, right? Only if we make sure
that it's unique
Thanks in advance
BRs
epekkar ***@***.***> 於 2023年11月13日 週一 下午12:08寫道:
… Hi,
uuid_11aa22bb_cac7_459a_a759_2eab2efd02ae is a Universally Unique
Identifier <https://en.wikipedia.org/wiki/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).
—
Reply to this email directly, view it on GitHub
<#2 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BDF3XNTHG2U5NBP6O2DSFD3YEGMMBAVCNFSM6AAAAAA7IQCNFCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMBXGQ2DMMJVGA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
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. |
hi,
Thanks for the explanation. It's really clear. But I'd like to ask why we
use UUID in ipxact:value in ipxact:moduleParameter instead of the real
value like 32 in AXI4_ADDRESS_WIDTH case?
Thanks in advance
BRs
epekkar ***@***.***> 於 2023年11月13日 週一 下午1:51寫道:
… 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.
—
Reply to this email directly, view it on GitHub
<#2 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BDF3XNXCL2MBO4LJONPGTILYEGYPVAVCNFSM6AAAAAA7IQCNFCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMBXGUYTKOJWHA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
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 . |
Hi,
Thanks a lot for the explanation!!! I'd like to ask that are you the author
of the ipxact structure in the pulpinoexperiment project?
I've been surveying the ipxact file recently and wondering why some SV file
don't have its ipxact file, such as data about dp_ram?
Thanks in advance~
BRs
epekkar ***@***.***> 於 2023年11月13日 週一 下午2:00寫道:
… 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 .
—
Reply to this email directly, view it on GitHub
<#2 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BDF3XNW5PRCDVVXVLINJE3TYEGZRRAVCNFSM6AAAAAA7IQCNFCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMBXGUZDEMRTHA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
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. |
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
The text was updated successfully, but these errors were encountered: