-
Notifications
You must be signed in to change notification settings - Fork 24
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
[Discussion - Numerous unrelated topics] #29
Comments
The It is hard to know exactly since you did not provide an example, but I suspect Try using the |
Hello Alex (A) File GenericCounter_rm.rdl (B) File GenericCounter_rm.rdl (C) File GenericCounter_w_intr_rm.rdl (D) File GenericCounter_w_type_rm.rdl thanks for your attention and support |
[A] [B & C] [D] The component type
Alternatively, you could completely remove the |
Thanks again for the effective exchange. A few more precisions please: [A] Do you have a prevision for the peakrdl-uvm update (apparently planned as milestone peakrdl-uvm version 3.0)? [B] & [C] Do i understand right, that these RDL concepts, intr and counter, are currently only processed by peak-regblock? [D] Clear. We have this extra hierarchy because other blocks combine Registerfile and Memoryfile. But indeed for peakrdl-regblock to work on these examples, i had indeed to remove the "extra" hierarchy. |
[A] [B & C] |
Morning Alex, two more questions please. [E] Adding basic support for hdl_path property in RDL exporter. Understand not full syntax from IPXACT is translatable, but the basic one is translatable and already useful. Cause for many this lacking translation implies extra post-processing scripting steps. [F] What about supporting in the 'peakrdl dump' a mode which explores the hierarchical output as documented here: cheers & regards |
[E] [F] |
According to documentation https://github.com/SystemRDL/PeakRDL-html it is possible to declare a internal addrmap in the RDL as top for the html output.
Tried to do so, declaring as top the Regfile addrmap instead as per default the last addrmap, which would be the Memorymap on my block.rdl file, but it was not accepted. The call and error messages are copied below:
...
top_node = 'BlocknameRegfile0'
peakrdl html --peakrdl-cfg {config_file} -t {top_node} -o {output_file} {input_file}
error msg
fatal: Elaboration target 'BlocknameRegfile0' not found
and double checked with "peakrdl dump" that the name is correct and recognised.
Any hints what could be the root cause?
thanks for your help and attention!
The text was updated successfully, but these errors were encountered: