Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • Jan 22 14:27
    sckoarn commented #1597
  • Jan 22 08:57
    m-kru commented #1618
  • Jan 22 05:11
    eine commented #1618
  • Jan 22 05:09
    eine commented #1618
  • Jan 21 21:13
    eine commented #1437
  • Jan 21 21:08
    eine commented #1437
  • Jan 21 21:02
    eine commented #1437
  • Jan 21 21:01
    Xiretza commented #1437
  • Jan 21 21:01
    Xiretza commented #1437
  • Jan 21 20:56
    m-kru commented #1437
  • Jan 21 20:32

    github-actions[bot] on nightly

    lsp testsuite: improve substitu… (compare)

  • Jan 21 19:53

    tgingold on master

    lsp testsuite: improve substitu… (compare)

  • Jan 21 16:43
    m-kru commented #1618
  • Jan 21 10:58
    m-kru commented #1618
  • Jan 21 10:33
    tmeissner commented #1618
  • Jan 21 10:33
    tmeissner commented #1618
  • Jan 21 10:15
    umarcor commented #1519
  • Jan 21 10:13
    m-kru commented #1618
  • Jan 21 10:11
    umarcor commented #1519
  • Jan 21 10:09
    umarcor commented #1519
eine
@eine
In ghdl/ghdl#1594, @Paebbels checked OSVVM tasks but not UVVM's. Maybe, since the first one is already failing, he didn't go ahead until the bug is fixed.
Tomas Correa
@tpcorrea
Depending on the uvvm version, there uvvm_util and uvvm_vvc_framework files change, so hard-coding is not the best idea.
Ok. As I wrote, I have a modified version of this script that could be reviewed and adopted.
eine
@eine
Which version of UVVM are you testing it with?
Tomas Correa
@tpcorrea
Right now I am in the v2_2020.04.20. It still has some issues in some modules, but I believe that now (with my script) the problem is with UVVM and not ghdl.
eine
@eine
Let me run a quick test.
Tomas Correa
@tpcorrea
With the v2020.05.19 (the last release), I had failures on VIP_AVALON_ST and VIP_ETHERNET. All the others compiled without error. (I just run a test.)
eine
@eine
Ok. Please, go ahead and open a PR.
Tomas Correa
@tpcorrea
Ok. I will do it tomorrow morning. Regards.
eine
@eine
I got the following when building that version with latest scripts:
Compiling library 'uvvm_vvc_framework' ...
  Analyzing package file '*\uvvm\uvvm_vvc_framework\src\ti_vvc_framework_support_pkg.vhd'
ghdl.exe : *\uvvm\uvvm_vvc_framework\src\ti_vvc_framework_
support_pkg.vhd:27:24: unit "ti_protected_types_pkg" not found in library "uvvm_vvc_framework"
Patrick Lehmann
@Paebbels
@tpcorrea I'll change the utility library and the framework to also load compile order from file lists. For order of components itself, I didn't know they finally managed to add a list for this too. So I can read this and order the dictionary by this list.
@tpcorrea to compile UVVM, you need this issue fixed: #1593
Tomas Correa
@tpcorrea
@Paebbels : There is still a typo error. The module is 'UVVM_VVC_FRAMEWORK, but you have defined the library inside the power script as UVVM_VCC_Framework. (VCC istead o VVC)
Patrick Lehmann
@Paebbels
@tpcorrea oh, I'll fix it. Comes with a next PR.
Anyway latest versions don't analyze. Do you have a UVVM version that could be used for testing the script?
eine
@eine
@Paebbels:
Patrick Lehmann
@Paebbels

@Paebbels:

I'm testing ...

eine
@eine
Let me know if I can help ;)
Patrick Lehmann
@Paebbels
@tpcorrea uvvm/uvvm@51f9287 works now. I'll also do some checks in the Bash variant of the script and then push a combined fix.
xiretza
@xiretza:xiretza.xyz
[m]
:point_up: January 14, 2021 1:36 PM FYI, gitter now has native matrix bridging, which offers less terrible search in my experience :)
eine
@eine
@xiretza:xiretza.xyz what is required for enabling that?
xiretza
@xiretza:xiretza.xyz
[m]
nothing, just join #ghdl1_Lobby:gitter.im.
eine
@eine
@tgingold, does ghdl/ghdl@39dacc4 mean that we can now pass verilog and vhdl files to GHDL when synthesising? I can understand how that would work with ghdl-yosys-plugin. What about ghdl --synth?
tgingold
@tgingold
No, this is a just a check of the file extension
xiretza
@xiretza:xiretza.xyz
[m]
haven't tested it yet, but will this now cause errors depending on the name of a file?
that'd be pretty awful imho
tgingold
@tgingold
Not an error but a warning. If you are using .v or .sv for a vhdl file, you are looking for troubles!
xiretza
@xiretza:xiretza.xyz
[m]
UNIX based systems don't generally care about any potential part of a filename after a period character, and as far as I can see the check triggers on any filename that doesn't end in .vhd(l) - but as long as it's only a warning, that's perfectly acceptable
eine
@eine
@tgingold, that makes sense. I personally like specifying VHDL sources and Verilog sources as different file groups. Therefore, I like it to be check/warning, not a feature.
T. Meissner
@tmeissner
Mhm, now I get warning with yosys for my ordinary *.vhd files :smirk: 
SBY 21:27:45 [work/psl_endpoint] base: warning: unexpected extension for vhdl file "pkg.vhd" [-Wlibrary]
SBY 21:27:45 [work/psl_endpoint] base: warning: unexpected extension for vhdl file "sequencer.vhd" [-Wlibrary]
SBY 21:27:45 [work/psl_endpoint] base: warning: unexpected extension for vhdl file "hex_sequencer.vhd" [-Wlibrary]
SBY 21:27:45 [work/psl_endpoint] base: warning: unexpected extension for vhdl file "psl_endpoint.vhd" [-Wlibrary]
tgingold
@tgingold
Humm, that's not expected!
tgingold
@tgingold
Looks like a stupid mistake. I thought I tested that...
T. Meissner
@tmeissner
Here with ghdl --synth only:
$ ghdl --synth --std=08 pkg.vhd sequencer.vhd hex_sequencer.vhd psl_logical_iff.vhd -e psl_logical_iff > /dev/null
ghdl:warning: unexpected extension for vhdl file "pkg.vhd" [-Wlibrary]
ghdl:warning: unexpected extension for vhdl file "sequencer.vhd" [-Wlibrary]
ghdl:warning: unexpected extension for vhdl file "hex_sequencer.vhd" [-Wlibrary]
ghdl:warning: unexpected extension for vhdl file "psl_logical_iff.vhd" [-Wlibrary]
...
Patrick Lehmann
@Paebbels
@m-kru maybe you can push on this issue in UVVM too: UVVM/UVVM#130
Patrick Lehmann
@Paebbels

@m-kru as followup on #1618
If you get UVVM_Community_VIPs to contain a scripts/components_list.txt I will provide you a --addons or --community option to the compile script.

Btw. what is UVVM_SUPPLEMENTARY, it contains a Wishbone directory.

Aaron Panella
@a-panella
Hi all, I think I found a bug that is related to one that is already reported ( Support for constants of unconstrained types lacks inferring sizes from default assignment #1589) I will submit an issue for it later when I have time. This was reported 12 days ago, is this something that is being worked on currently?
tgingold
@tgingold
@a-panella Not yet.
Aaron Panella
@a-panella
@tgingold thanks for the reply - what I was doing was a pretty weird case anyway, so I'm not really surprised it doesn't work. It was passing a constant record type as an argument to an impure function with some other things (trying to emulate something similar to KWargs)
will provide a reproducable example later
mariuselv
@mariuselv
@Paebbels UVVM_SUPPLEMENTARY is UVVM, but with all documentation source files and testbenches and scripts; i.e. as we have it on our development server. The wishbone folder is a «work in progress» and used by some of the testbenches for verifying the DUVs.
umarcor
@umarcor
@mariuselv, what's the difference between the wishbone in the supplementary and the community repositories? Is it exactly de same code?
mariuselv
@mariuselv
@umarcor there should not be any differences, but if there is the community repository version is probably the oldest.
Patrick Lehmann
@Paebbels
@mariuselv so UVVM/UVVM is not the official repository?
mariuselv
@mariuselv
@Paebbels UVVM/UVVM is the official repository and the one you should get and use.
umarcor
@umarcor
@mariuselv, does it mean that wishbone features in the community repo are not to be used?
mariuselv
@mariuselv
@umarcor you can use it, but its a beta and not fully release yet.
Patrick Lehmann
@Paebbels
so to summarize:
  • UVVM is the only and only official repo
  • UVVM_SUPPLEMENTARY is to be ignored
  • UVVM_Community_VIPs will move to UVVM soon
Btw. why does UVVM and UVVM_SUPPLEMENTARY contain docs, while you mentioned that's the purpose of UVVM_SUPPLEMENTARY ?
mariuselv
@mariuselv
UVVM is the official repo and UVVM_SUPPLEMENTARY is as UVVM, but including source files, e.g docx files for documentation and testbenches used for verifying UVVM. I do not know what will happend to Community VIPs in the future, but nothing is planned yet.