Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • 20:05
    LarsAsplund commented #209
  • 16:33
    umarcor commented #880
  • 16:00
    LarsAsplund commented #880
  • 15:58
    LarsAsplund commented #880
  • 15:24
    eine labeled #845
  • 15:24
    eine labeled #845
  • 15:24
    eine milestoned #845
  • 15:24
    eine milestoned #845
  • 15:23

    eine on aldec-vhdl-2019

    (compare)

  • 15:23
    eine labeled #875
  • 15:23
    eine labeled #875
  • 15:23
    eine milestoned #875
  • 15:23
    eine milestoned #875
  • 15:23
    eine labeled #870
  • 15:23
    eine labeled #870
  • 15:23
    eine milestoned #870
  • 15:23
    eine milestoned #870
  • 15:23

    eine on python311

    (compare)

  • 15:22
    eine labeled #869
  • 15:22
    eine labeled #869
T. Meissner
@tmeissner
Yeah, a FAE of them meant that with the PolarFire version they would do a complete rewrite. However, the GUI looks exactly like the old one, so it seems it's the same odd code base :(
Bradley Harden
@bradleyharden
@tmeissner, when I created a container for QuestaSim, I used their installer in a fresh Ubuntu container, and when the install finished, I dumped a list of all installed packages in the container. I then diff'ed that list against a list from a fresh container, before install.
That worked really well to get the package list. Would that work well for Libero too?
Or is there some reason that won't work well?
T. Meissner
@tmeissner
I don't know what exactly you mean, the libero installer don't installs the neccessary linux packages, you have do that by hand
There is a document from Microsemi which lists (almost) all linux packages, which Libero needs.
Our Dockerfile for Questa is pretty simple, it only untars the Questa installation
We also install questa before in a clean environment and tar the instalattion directory. Questa itself seems to not needed any linux packages in addition
Bradley Harden
@bradleyharden
I installed Questa once, with a batch install script generated by their tool. Since then, I've just been copying the files when I make new containers. But I think the Questa installer must have installed some packages, because the container had more than it started with. At least that's what I remember. Maybe I'm mis-remembering
T. Meissner
@tmeissner
Oh, I didn't know, that Mentor installer has an option to generate a batch installer?
Bradley Harden
@bradleyharden
It's disappointing that Microsemi can't even be bothered to write a quick bash script to install packages for you 😕
I read this before installing Questa in a container for the first time
T. Meissner
@tmeissner
Cool, thanks :)
Bradley Harden
@bradleyharden
@eine, I have never tried to install Questa on Windows. I made the container for my own usage, targeting Linux. However, there are others in my group who primarily use Windows. I wanted to see how easy it would be to adapt my container workflow for them.
Apparently it's harder than I thought it would be
I don't know if it's the VPN or some artifact of Docker on Windows
T. Meissner
@tmeissner
You should avoid Windows at all costs when doing EDA ;)
Bradley Harden
@bradleyharden
I might try to install Docker on one of our Cloud VMs and see if the VPN is the cause
NanooooK
@NanooooK
QuestaSim is in 64 bits? I had to add several 32 bits library for ModelSim to start, they aren't provided with the installer.
Bradley Harden
@bradleyharden
@tmeissner 😑
T. Meissner
@tmeissner
Yes, Questa is 64 bit
Modelsim has a 32 bit binary, We had to install 3 further 32 bit packages to run it
T. Meissner
@tmeissner
@NanooooK It's not easy to get the Dockerfiles out of our internal network, I hope you have patience ;)
NanooooK
@NanooooK
Don't worry there is no rush :)
Yatekii
@Yatekii
argh I wanna kms ... xilinx tooling is absolute garbage ...
I wanna use nice tools :(
eine
@eine

Questa itself seems to not needed any linux packages in addition

Note that this might be not the same on Fedora containers: https://github.com/eine/hwd-ide/wiki/Continuous-Integration-(CI)#modelsimquestasim-inside-fedoralatest

Anyway, I also suggest the same approach as @tmeissner: to install in a clean container and then tar the installation directory: https://github.com/mviereck/x11docker/issues/201#issuecomment-558990580

Oh, I didn't know, that Mentor installer has an option to generate a batch installer?

It does. But, AFAIK, you do need to run the GUI installer in order to generate it. Hence, it's does not solve the issue if you cannot run the GUI in the first place.

I have never tried to install Questa on Windows. I made the container for my own usage, targeting Linux. However, there are others in my group who primarily use Windows. I wanted to see how easy it would be to adapt my container workflow for them.

@bradleyharden, I meant to start with flexlm only. Forget about Questasim, for now, as it is unrelated. You should be able to execute lmutil on Windows (on the host) and check the connection to the server. Then execute lmutil in any container (just extract it on the host and mount/bind it in the container).

Of course, you need two different lmutil artifacts: for Windows and for GNU/Linux.
Fortunately, you should find it everywhere: Xilinx, Altera, Lattice, Mathworks, Autodesk...
Lars Asplund
@LarsAsplund
@all For some reason I cannot give thumbs up on this one but if you agree please give it a try. https://forums.xilinx.com/t5/Simulation-and-Verification/Add-support-for-VUnit/td-p/1098552
Bradley Harden
@bradleyharden
I'd tried. Couldn't thumbs-up either
It must be one of these
Lars Asplund
@LarsAsplund
@all Logged out and in again. Now i works
Rafael Pereira
@rafaelnp
I am new to vunit, and starting by running on Linux the examples and I got this error using ghdl, could not find a solution elsewhere, any hints?
python run.py -v lib.tb_example.all
Compiling into vunit_lib: ../../../usr/lib/python3.8/site-packages/vunit/vhdl/string_ops/src/string_ops.vhd                        failed
=== Command used: ===
/usr/bin/ghdl -a --workdir=/home/dev/tmp/vunit_out/ghdl/libraries/vunit_lib
--work=vunit_lib 
--std=08 -P/home/dev/tmp/vunit_out/ghdl/libraries/vunit_lib
-P/home/dev/tmp/vunit_out/ghdl/libraries/lib 
/usr/lib/python3.8/site-packages/vunit/vhdl/string_ops/src/string_ops.vhd

=== Command output: ===
/usr/lib/python3.8/site-packages/vunit/vhdl/string_ops/src/string_ops.vhd:12:10: unit "numeric_std" not found in library "ieee"
/usr/lib/python3.8/site-packages/vunit/vhdl/string_ops/src/string_ops.vhd:99:22: no declaration for "unsigned"
...
/usr/lib/python3.8/site-packages/vunit/vhdl/string_ops/src/string_ops.vhd:118:14: package "string_ops" was not analysed
/usr/bin/ghdl: compilation error
Lars Asplund
@LarsAsplund
@all Keep the kudos coming if you're interested. I think that showing market interest is the only way to get this working properly. We filed bug reports years ago but that didn't help.
image.png
T. Meissner
@tmeissner
Is this the same login as for the Xilinx website?
Lars Asplund
@LarsAsplund
yes
T. Meissner
@tmeissner
I will try to vote after I found my login credentials ;)
T. Meissner
@tmeissner
Voted :)
Carlos Alberto Ruiz Naranjo
@qarlosalberto
+1
NiJen
@NiJen
+1
Lars Asplund
@LarsAsplund
@NiJen @qarlosalberto @tmeissner Brilliant, now we have 7 votes. I think 25 would be sufficient to show great commercial interest
Tiago Gomes
@tasgomes
+1
GlenNicholls
@GlenNicholls
@LarsAsplund I was able to vote this morning. I had problems last night as well
GlenNicholls
@GlenNicholls
@rafaelnp Which version of GHDL are you using? Do you have the bin/ directory in your path? Is ieee defined under <ghdl install folder>/lib/ghdl/ieee? It looks like your install works correctly to me since it doesn't complain about calling ghdl. Not sure if this helps, but I also add vu.set_compile_option('ghdl.a_flags', ['--ieee=synopsys', '-frelaxed-rules']) to my run.py
Rafael Pereira
@rafaelnp

@GlenNicholls Thanks for your reply. I added the line you suggested, no difference.
Listing the ghdl package files, I found:

/usr/bin/ghdl
...
/usr/lib/ghdl/ieee/v08/ieee-obj08.cf
/usr/lib/ghdl/ieee/v87/ieee-obj87.cf
/usr/lib/ghdl/ieee/v93/ieee-obj93.cf
...
/usr/lib/ghdl/src/openieee/math_real-body.vhdl
/usr/lib/ghdl/src/openieee/math_real.vhdl
/usr/lib/ghdl/src/openieee/upf-body.vhdl
/usr/lib/ghdl/src/openieee/upf.vhdl
/usr/lib/ghdl/src/openieee/v08/std_logic_1164-body.vhdl
/usr/lib/ghdl/src/openieee/v08/std_logic_1164.vhdl
/usr/lib/ghdl/src/openieee/v87/numeric_bit-body.vhdl
/usr/lib/ghdl/src/openieee/v87/numeric_bit.vhdl
/usr/lib/ghdl/src/openieee/v87/numeric_std-body.vhdl
/usr/lib/ghdl/src/openieee/v87/numeric_std.vhdl
/usr/lib/ghdl/src/openieee/v87/std_logic_1164-body.vhdl
/usr/lib/ghdl/src/openieee/v87/std_logic_1164.vhdl
/usr/lib/ghdl/src/openieee/v93/numeric_bit-body.vhdl
/usr/lib/ghdl/src/openieee/v93/numeric_bit.vhdl
/usr/lib/ghdl/src/openieee/v93/numeric_std-body.vhdl
/usr/lib/ghdl/src/openieee/v93/numeric_std.vhdl
/usr/lib/ghdl/src/openieee/v93/std_logic_1164-body.vhdl
/usr/lib/ghdl/src/openieee/v93/std_logic_1164.vhdl
/usr/lib/ghdl/synopsys/v87/ieee-obj87.cf
/usr/lib/ghdl/synopsys/v93/ieee-obj93.cf

The Ghdl version is 0.37 and VUnit is 4.4.0. My $PATH is /usr/bin:/usr/games:/home/dev/bin:/usr/local/sbin:/usr/local/bin:/usr/lib/jvm/default/bin:/home/dev/.local/bin. Is there maybe an undocumented configuration or dependency?