04-24-2020 08:30 AM
Other people have run into similar problems, figured I'd raise this one too. Using Vivado 2018.3 and OSVVM 2018.04.
First is the problem several people have mentioned, the unsupported call to std.textio.tee. I patched this by replacing TrancriptPkg.vhd:176 with
-- RG 04-20-2020 Removed/replaced for Xilinx Vivado compatibility -- TEE(TranscriptFile, buf) ; WriteLine(TranscriptFile, buf) ; WriteLine(OUTPUT, buf) ;
That lets me get to the next problem, which sure seems like a parser bug.
ERROR: [VRFC 10-837] illegal named association in array index [/home/rgaddi/Documents/work/P500/23C501/src/testbench/osvvm/CoveragePkg.vhd:2920] ERROR: [VRFC 10-837] illegal named association in array index [/home/rgaddi/Documents/work/P500/23C501/src/testbench/osvvm/CoveragePkg.vhd:2932] ERROR: [VRFC 10-837] illegal named association in array index [/home/rgaddi/Documents/work/P500/23C501/src/testbench/osvvm/CoveragePkg.vhd:2944] ERROR: [VRFC 10-837] illegal named association in array index [/home/rgaddi/Documents/work/P500/23C501/src/testbench/osvvm/CoveragePkg.vhd:2957] ERROR: [VRFC 10-837] illegal named association in array index [/home/rgaddi/Documents/work/P500/23C501/src/testbench/osvvm/CoveragePkg.vhd:3022]
Those lines in CoveragePkg aren't an array indexing operation, they're a subprogram call to the CovPType.WriteBin as defined on line 2832.
Any idea what's going on here?
04-24-2020 08:40 AM
Update: The protected method in question was only defined in the protected body, not in the public API for the protected type. I copied the declaration up to the public section and now fail with the message
ERROR: [VRFC 10-1287] protected type method argument cannot be file or access type
That's information, but it's not progress.
04-24-2020 11:10 AM
I wouldnt bother trying. OSVVM using a lot of VHDL 2008 that XSIM has no good support for. You're better off using GHDL (open source VHDL simulator) or the free version of modelsim that Intel Provide.
04-24-2020 11:26 AM
Probably right, though certainly disappointing. And I'm sure the answer to "why doesn't the simulator have full 2008 support" will remain "Well, no one ever asks for it."