@mmicko For the GHDL plugin: I am pretty sure there are cross-compilers for the windows targets. I am not sure for Darwin even if theorically that should be possible too.
For the standard libraries, there is no need to create the object files as they are used only for simulation. The standard libraries should be analyzed once, but the result is a text file that is portable (although I fear this hasn't been tested).
For the standard libraries, there is no need to create the object files as they are used only for simulation. The standard libraries should be analyzed once, but the result is a text file that is portable (although I fear this hasn't been tested).
Thanks @umarcor for very detail answer, will check links you have provided regarding docker solutions, and have to think of best way of providing that. As you pointed out it is one-man-project so some things take time, and also there are other things I do. So will solve things like GHDL integration and docker environment , but some of that may take time due to proiorities
@tgingold will probably jump in here with more questions when time comes :)
I am pretty sure there are cross-compilers for the windows targets.
@tgingold maybe you mean https://github.com/hackfin/ghdl-cross.mk ? I think that is different. That generates a GHDL to be executed on Linux, which will produce simulation models for Windows. But GHDL itself is not cross-compiled.
@mmicko, absolutely no pressure or rush at all. Having a solid and stable open source EDA ecosystem is a mid-long term project that requires a lot of people to coordinate. We will get there, step by step.
@bkzshabbaz, please provide the full context of what you are trying to achieve. It seems that you are trying to use GHDL, ghdl-yosys-plugin and Yosys for synthesising a VHDL design targeting an ECP5 device?
See the following references:
- ghdl-yosys-plugin examples: https://github.com/ghdl/ghdl-yosys-plugin/blob/master/library/ecp5u/components.vhdl#L3993
- fomu-workshop: https://github.com/im-tomu/fomu-workshop/blob/master/hdl/sb_ice40_components.vhd
- neorv32: https://github.com/stnolting/neorv32/blob/master/boards/UPduino_v3_ghdl-yosys-nextpnr/sb_ice40_components.vhd
Those three examples are based on Makefiles. However, each of them uses an slightly different style and source organisation.
I brought this up in the ulx3s gitter chat and they mentioned the oddrx1f component isn't capitalized.
@gatecat
It should be in capitals
I suspect there is some kind of GHDL issue going on here but don't know how to fix it
It should be in capitals
I suspect there is some kind of GHDL issue going on here but don't know how to fix it
See ghdl/ghdl#1682. Not exactly the same, but also related to upper casing between GHDL and one specific variant of yosys.
However, it could be handled by an specific option in yosys.
Will get a MWE branch up soon.
Hi everyone!
I am trying to install ghdl-ls on my WSL Ubuntu 18.04. Everything looks fine, but when I am calling ghdl-ls I got following:
Traceback (most recent call last):
File "/home/arnfol/anaconda3/bin/ghdl-ls", line 5, in <module>
from pyGHDL.cli.lsp import main
File "/home/arnfol/anaconda3/lib/python3.8/site-packages/pyGHDL/cli/lsp.py", line 44, in <module>
import pyGHDL.libghdl as libghdl
File "/home/arnfol/anaconda3/lib/python3.8/site-packages/pyGHDL/libghdl/__init__.py", line 149, in <module>
libghdl = _initialize()
File "/home/arnfol/anaconda3/lib/python3.8/site-packages/pyGHDL/libghdl/__init__.py", line 131, in _initialize
_libghdl_path = _get_libghdl_path()
File "/home/arnfol/anaconda3/lib/python3.8/site-packages/pyGHDL/libghdl/__init__.py", line 126, in _get_libghdl_path
raise Exception("Cannot find libghdl {}".format(basename))
Exception: Cannot find libghdl libghdl-2_0_0_dev.soHere is my installation script:
#!/usr/bin/env bash
sudo apt-get install -y libz-dev
sudo apt-get install -y gcc gnat
# get & install GHDL
git clone https://github.com/ghdl/ghdl.git
cd ghdl
mkdir build && cd build
../configure --prefix=/opt/ghdl
make && make install
# install PyGHDL
cd ..
pip3 install .What am I doing wrong?
found the libghdl in
/opt/ghdl/lib/libghdl-2_0_0_dev.so and here is my ghdl --dispconfig output:command_name: /opt/ghdl/bin/ghdl
command line prefix (--PREFIX): (not set)
environment prefix (GHDL_PREFIX): (not set)
exec prefix (from program name): /opt/ghdl
library prefix: /opt/ghdl/lib/ghdl
library directory: /opt/ghdl/lib/ghdl
default library paths:
/opt/ghdl/lib/ghdl/ieee/v93/
/opt/ghdl/lib/ghdl/Locate the directory where the shared library is installed.
Search order:
GHDL_PREFIX- directory (prefix) of the vhdl libraries.VUNIT_GHDL_PATH- path of theghdlbinary when using VUnit.GHDL- name of, or path to theghdlbinary.- Try within
libghdl/Python installation.- Try when running from the build directory.
Running
GHDL_PREFIX=/opt/ghdl/lib/ ghdl-ls cause the same error
Did you try
GHDL=/opt/ghdl/bin/ghdl ghdl-ls?
I think that GHDL_PREFIX needs to point to a subdir of lib:
GHDL_PREFIX=/opt/ghdl/lib/ghdl ghdl-ls
Does GHDL support VHDL-2019 Interfaces? Is there any documentation on what language features are supported/missing in each language revision? Something like this maybe?
I ran into type-generic entities not being supported last night =/ and a coworker is asking about interfaces.
So, the plumbing for achieving something similar to https://github.com/SymbiFlow/sv-tests (https://symbiflow.github.io/sv-tests-results/) is almost there... except we don't have a set of tests that matches all the features in the language.
Not at all. All the known info is whatever you can get by watching the repo and inspecting the commits that Tristan pushes. There is no further roadmap other than that. There is https://github.com/ghdl/ghdl/wiki as very general guidelines, but most of the features are added by surprise.
The same applies to bug fixes. If Tristan replies to an issue saying he is looking at it, you might expect a fix in a few hours/days. Otherwise, it can take weeks or months.
The same applies to bug fixes. If Tristan replies to an issue saying he is looking at it, you might expect a fix in a few hours/days. Otherwise, it can take weeks or months.
I know that Tristan wants to support generics, external names and unconstrained arrays, which are the three most relevant missing VHDL 2008 features. However, those are complex, because the elaboration model is very different from previous revisions. He was sidetracked with synthesis 2-3 years ago, which I believe we are all very thankful about. Lately, there have been several comments about Rust, JIT (deprecating GCC), supporting merging multiple revisions, etc. I believe all of those are small steps towards being able to implement 2008 and 2019 features properly. Nonetheless, that won't be quick.
With regard to interfaces, as valuable as I think they are, I would expect them to be added after the main 2008 features are done. Interfaces are more useful with generic types and unconstrained arrays.
With regard to interfaces, as valuable as I think they are, I would expect them to be added after the main 2008 features are done. Interfaces are more useful with generic types and unconstrained arrays.
Other than that, as you might already know, these last months we've been talking about proposing some kind of "VHDL Foundation" in order to be able to handle funds/donations and hopefully hire Tristan partially (through an agreement with his current employer). That is the very main priority we all agree on: having an open source implementation of the language which can be used as a reference. Once GHDL supports 2008 and 2019, it might be feasible to implement upcoming LCS after they are approved but before the standard is released. Yet, that's something that no single human can do. We can neither ask nor allow Tristan to do that himself. We need to scale.
The main problem is who is going/willing to manage that. I am "a child" and I don't have the economical stability for doing that. Someone or a group of people needs to step ahead, which "the community" accepts as legit for making good use of whichever resources are gathered in the name of "improving the open source VHDL ecosystem (tooling, tests, libraries, learning/teaching material...)".
The main problem is who is going/willing to manage that. I am "a child" and I don't have the economical stability for doing that. Someone or a group of people needs to step ahead, which "the community" accepts as legit for making good use of whichever resources are gathered in the name of "improving the open source VHDL ecosystem (tooling, tests, libraries, learning/teaching material...)".
Note that the "VHDL Foundation" is just a concept. In practice, it would probably be some group in an existing foundation. However, it needs not to be IEEE, because there would be conflicts of interest.
In the VASG meeting before the last one, I commented this with @JimLewis and @Paebbels. I had been mostly thinking about it from a EU perspective, and discussing it with @LarsAsplund. However, EU funds might be limited to EU citizens. Jim might try to replicate the same in the US. It would be nice if you, @marlonjames, @GlenNicholls and others could somehow coordinate.
For now, I created a private repository in my namespace in GitLab, where I'm gathering all the references and ideas in this regard. It's a pot-pourri yet, and there might be some sensible references, so I don't want to make it public. However, I have no problem for sharing it with you or others who are interested.
For now, I created a private repository in my namespace in GitLab, where I'm gathering all the references and ideas in this regard. It's a pot-pourri yet, and there might be some sensible references, so I don't want to make it public. However, I have no problem for sharing it with you or others who are interested.
