airhdl Feature Requests
40 results found
-
Specify base addresses in the project space instead of the register map
When adding a register map to a project I want to be able to specify the base address of that map in the project, not in the register map itself. This will allow for the use of library modules that may be used multiple times in the current project, or in multiple projects where the base address is different.
1 vote -
Add a download button for projects
It would be very useful for us to be able to generate the output files for a whole project, so having a “Download” button also for projects would be ideal.
2 votes -
Add register input/output pipeline option using generic
Hello,
In order to help timing closure, it would be extremely helpful to add an option to insert extra register for input/outputs.
I suggest that each register (or array) would have a generic associated with the number of extra register pipeline we want to insert :GREG1OUTEXTRAPIPE := 0; -- no extra pipeline
GREG1INEXTRAPIPE := 0; -- no extra pipeline
GREG2OUTEXTRAPIPE := 1; -- 1 register per REG1 out field added
GREG2INEXTRAPIPE := 2; -- 4 register per REG2 in field addedThis will…
1 voteHi Guillaume, thanks for suggesting this. We'll be looking into it.
-
Add a global download button
Add a download button to the Register Maps view to allow downloading several register maps (e.g. JSONs) at once.
5 votes -
Allow adding shared register map(s) to a project
Currently only register maps that you have created yourself can be added to a project. This is a suggestion to allow adding register maps that have been shared with you by another user to a project.
1 vote -
Option to auto update offset addresses
I am preparing a new register map and I'm worried that if I create 200 registers and tomorrow I want/need to add a new register in the possition 100, I have to manually increase the offset addresses from the 100 to 200 registers.
2 votesExcellent suggestion, thank you very much. I’m logging this as a development ticket.
-
Unique Register Address when duplicating
When duplicating a register, it would be nice to have the new available address offset filled in the new register instead of the offset of the original one.
1 vote -
Option for an external register implementation
I'd like to be able to set an option that the register will be implemented outside of the airhdl model.
My use case is that I want to be able to reset a single register in a different way with respect to all the others: all registers must be reset from a software reset instead of one that need not to be reset by software, but only at power up.
0 votes -
Landing page
It would be nice if one could choose its landing page (Dashboard, projects, or maps) in the user configuration
1 vote -
Would it be possible to merge a set of register maps in a single one?
Maybe this is already possible with JSON upload. But in simple cases one would like to merge exixting maps in a single one by simply specifying the offset of one map respect to the other.
1 vote -
Hierarchical register structure
Allow registers to be put in a directory type structure.
8 votes -
add version management
The versions are tracked, however occasionally there is need to generate files from an earlier version, or roll back a set of register changes, possibly with the inclusion of labels.
< the logical extension is branching and merging that is less typical in register maps than mainline code >2 votes -
Self-clearing fields should be banned on read-only registers
Self-clearing fields should be banned on read-only registers, since they don't make sense. In fact those fields are not cleared after read.
The web interface could simply generate a DRC error.1 vote -
add Software set, hardware clear register type
Currently there is an hardware set, software clear type (interrupt)
Adding a software set, hardware clear type would allow the 'arming' of hardware state machines by software, the bit can then be automatically cleared by hardware, ready to re-arm the state machine in future.1 vote -
Support bit-level RW access types
As is, access granularity is defined at the register level. However certain bits may require accessibility in ways that others may not. This is a recurring theme on many designs I have worked on.
I think it would be useful to specify for example, that Reg[7] is Read-only, while Reg[6] is Write-only, and Reg[5:0] is R/W.
6 votes -
Support longer text in register overview graphic
The visualization of the register fields arrays the text in a manner that renders it less than helpful unless all bit fields are shorter than 4 characters (except in the case of wider bit fields).
One solution might be to rotate field names 90 degrees and situate them vertically.
2 votesThanks for your suggestion. We’ll try to improve this aspect of the register overview in the future.
-
Option for synchronous reset of axi interface
To get the maximum performance, and smallest of a design the same type of reset should be used throughout the design, according to this document: https://www.xilinx.com/support/documentation/white_papers/wp275.pdf
This register generator currently uses asynchronous reset. It would be nice to have an option to use synchronous reset. If the reset of the design uses synchronous reset, all flip-flops would use the same type of reset and can be implemented directly into the flip-flop yielding better performance and are usage. Currently there is no way of changing the type of reset, which is unfortunate if used in a design that implements synchronous reset.
3 votes -
Add option to split register arrays and still create one single array output
Add the ability to split register arrays up in equal parts and generate single array output.
Ex.
Register:
| [7:0] | [7:0] | [7:0] | [7:0] |Each element in the array would be 8 bits long instead of 32, but still be apart of the same array.
Current solution would generate 4 different array outputs.
1 vote -
Add option to not generate strobe port
Sometimes the strobe port is not needed and generated unnecessary ports
Would be nice to have an option to not generate this port so in the sblock design the module will look nicer.4 votes -
Wrap records on a register basis
Be able to select registers to be wrapped in records. This will allow the user to select only the registers he want to use records. The rest will use regular signals.
1 vote
- Don't see your idea?