vhdl

[...] since the increase to 64-bit wide busses, using drop-down lists to choose the bit width and selecting bits is tedious, [...]

By @maehne in #617 (comment)

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

Several users have asked for an example of how to use the makefiles in projects that contain precompiled and/or encrypted IP cores or libraries. There should be a simple example. It will likely not work for them, but could act as a template.

Alternatively, documentation or an explicit API for these objects would also help.

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

It would be cute to be able to identify the source code from which a particular microwatt cpu implementation was built. If the build process could look for the git SHA1 ID of the current head and include that as a constant value in the build, hooked up to the syscon framework so it could be read by MMIO, that could be useful. We would probably want (say) 32 bits of SHA1 plus a dirty flag.

Then

Create NeoVim integration of VHDL language server and publish instructions on how to use it.