vhdl
Here are 1,768 public repositories matching this topic...
Revisit CLI syntax
Currently, the architecture of the CLI is based on (sub)commands and options. Commands are expected to be provided as the first argument, and do effectively decide which feature is to be used. OTOH, options provide parameters to the commands. However, there is no syntactical difference, as both commands and options start with --
or -i
. As a result, we rely on properly formating --help
and on
-
Updated
May 2, 2022 - Haskell
#23 was closed, and a follow on action was to document how to configure the cocotb logger to separate it and the simulator stdout.
-
Updated
Apr 29, 2022 - VHDL
-
Updated
Apr 28, 2022
Here is the problem:
$ make compile
Traceback (most recent call last):
File "C:\My_Designs\probe_fpga_design_1\run.py", line 336, in
main()
File "C:\My_Designs\probe_fpga_design_1\run.py", line 181, in main
vu.add_osvvm()
File "c:\my_designs\probe_fpga_design_1\deps\vunit\vunit\ui_init_.py", line 1030, in add_osvvm
self.builtins.add("osvvm")
File "c:\my
Currently we don't reset registers or we use :=
initalisers when defining signals.
This works ok in FPGAs and ghdl sim but sucks for ASIC and gate level sim as it causes a lot of X state propagation issues.
Scrub all of the code to add resets to register state.
-
Updated
Nov 29, 2020 - VHDL
-
Updated
Apr 14, 2022 - Python
-
Updated
Apr 30, 2022 - Python
-
Updated
Apr 12, 2022 - JavaScript
-
Updated
Jan 5, 2019 - VHDL
-
Updated
Apr 18, 2022
-
Updated
Nov 23, 2021 - VHDL
-
Updated
Mar 27, 2022 - C++
-
Updated
Apr 29, 2022 - VHDL
-
Updated
Sep 22, 2020 - C++
Create NeoVim integration of VHDL language server and publish instructions on how to use it.
Improve this page
Add a description, image, and links to the vhdl topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the vhdl topic, visit your repo's landing page and select "manage topics."
We had so far 3 tickets (issues #862, #1324, #1434) plus several occasions in the classroom, where users thought simulation was broken in Logisim-evolution due they had inadvertently activated "Printer view" in Preferences-> Layout. So, it seems that this functionaly is causing more confusion than added value. I see its only value when exporting circuits as an image. IMHO, we should either remove