We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
If I use a generic of type TIME in my testbench, it seems I cannot alter the value of said generic from the python script.
Example:
Defintiion at the TB top level design g_clk_axi : TIME := 4 ns;
The python script statement: tc_debug_0.set_generic("g_clk_axi", "4ns")
vsim message:
The normal vsim use would be -gg_clk_axi=4ns but as vuint parses the above to -gg_clk_axi="4ns" it does not work.
Is tere any other way of controlling the TIME generic?
The text was updated successfully, but these errors were encountered:
I can see if I can make it work. In the meantime you could make it a string generic and use time'value to convert to a time value in VHDL.
time'value
Sorry, something went wrong.
Sounds good. I can us this work-around for the time being. Thanks!
Fixes issue #86. Setting generic of type time.
3ea41dc
You should be able to set generics of type time now. Expect if you use GHDL.
No branches or pull requests
If I use a generic of type TIME in my testbench, it seems I cannot alter the value of said generic from the python script.
Example:
Defintiion at the TB top level design
g_clk_axi : TIME := 4 ns;
The python script statement:
tc_debug_0.set_generic("g_clk_axi", "4ns")
vsim message:
** Warning: (vsim-3351) Invalid value ""4ns"" for generic "g_clk_axi". Not using this value.
The normal vsim use would be -gg_clk_axi=4ns but as vuint parses the above to -gg_clk_axi="4ns" it does not work.
Is tere any other way of controlling the TIME generic?
The text was updated successfully, but these errors were encountered: