Jump to content

Marco Ramirez

  • Posts

  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Marco Ramirez's Achievements


Member (1/2)



  1. Hi Philipp, I recompiled both SystemC and UVM-SystemC with both CXXFLAGS=-std=c++11 and CXXFLAGS=-std=c++17 and the result is the same, all SystemC tests pass but 14 of 15 of UVM-SystemC tests fail. I even tried with and without pthreads but it made no difference.
  2. Hi, I am trying to install uvm-systemc beta 3 in macOS Big Sur. The installation process seems to complete correctly but when running the checks all the tests fail. They do start running but at some point they stop and give a very simple error message. For example, here is the output of hello_world example: SystemC 2.3.3-Accellera --- Nov 15 2020 22:18:25 Copyright (c) 1996-2018 by all Contributors, ALL RIGHTS RESERVED Universal Verification Methodology for SystemC (UVM-SystemC) Version: 1.0-beta3 Date: 2020-07-08 Copyright (c) 2006 - 2020 by all Contributors See NOTICE file for all Contributors ALL RIGHTS RESERVED Licensed under the Apache License, Version 2.0 UVM_INFO ../../../src/uvmsc/base/uvm_root.cpp(343) @ 0 s: reporter [UVMTOP] UVM testbench topology: -------------------------------------------- Name Type Size Value -------------------------------------------- top top - - consumer consumer<T> - - producer1 uvm::uvm_component - - producer2 uvm::uvm_component - - -------------------------------------------- UVM_INFO @ 0 s: reporter [RNTST] Running test ... UVM_INFO producer.h(55) @ 0 s: top.producer1 [producer1] Starting. UVM_INFO producer.h(73) @ 0 s: top.producer1 [producer1] Sending producer1-0 UVM_INFO producer.h(55) @ 0 s: top.producer2 [producer2] Starting. UVM_INFO producer.h(73) @ 0 s: top.producer2 [producer2] Sending producer2-0 zsh: abort ./test It seems all processes run at least once but when the kernel advances the simulation something goes wrong. Has anyone seen this behaviour? Were you able to determine the its cause? Thanks for your help.
  3. Hi all, I found the problem. I was not aware the configure script compiles and runs a couple of small programs to perform some checks, since my installation path is not standard the linker wasn't able to find the libraries. The quick fix was to add systemc's lib directory to LD_LIBRARY_PATH. Another thing that seemed to have caused problems was that initially I installed SystemC without architecture suffix, so the library directory was simply called lib. It was until I re-installed including the architecture suffix that uvm-systemc configuration script was happy. Perhaps there is a parameter to change this behaviour but I didn't try.
  4. Hi, I am trying to install uvm-systemc beta 3 library but when I run the configuration script I always get the same error: configure: error: Non IEEE 1666 compatible SystemC version found, make sure that SystemC can be found and you build with the same compile options as building SystemC I am using Ubuntu 18.04.1 LTS and GCC 7.5.0 both of which are marked as tested in the release notes. Does anybody know a possible cause for this error? What parameters did you use for the configuration script? Thanks Marco
  • Create New...