Roman Popov

Members
  • Content count

    95
  • Joined

  • Last visited

1 Follower

About Roman Popov

  • Rank
    Advanced Member

Recent Profile Visitors

234 profile views
  1. Hello, All the answers can be found in standard: http://standards.ieee.org/getieee/1666/download/1666-2011.pdf Questions are tricky, so it's hard to guess answers without reading documentation carefully. Especially: Afaik, standard does not prohibit running processes in parallel, in case it is invisible to user. So implementation of standard can run some processes in parallel. But Accellera opensource SystemC implementation is single-threaded.
  2. Yes, I do this kind of conversion of TLM-1.0 to TLM-2.0 and vice versa very often, because for synthesis only TLM-1.0 is supported, and for VP TLM-2.0 is commonly used. The converter will be application-specific, because TLM-1.0 has no standard payload (Many TLM-1.0 models even define their own interfaces, instead of using standard put/get ).
  3. I've needed it for test environment modeling purposes, not for synthesis. Delta delay problems (also known as Shoot-thru) are possible in synthesizable SystemC. Common case is when you have a clock gate that inserts a delta delay into a clock signal distribution network. However in SystemC it is solved in a different way: Instead of delaying all assignments, you use immediate notifications inside clock signal, so that processes sensitive to gated clock are executed in the same delta cycle with processes sensitive to ungated clock.
  4. -isystem libs/systemc-2.3.1a/include This line looks suspicious. Should not it be something like -I/path/to/systemc/include ?
  5. Well, it's not compiling because con_arrayfifo is not a member of arrayfifo... You should declare it as a method in class body.
  6. In general google test was not designed for hardware verification, probably you should better look on UVM-SystemC when it will be released.
  7. Do you create a separate executable for individual test? More related discussions here: https://stackoverflow.com/questions/43145530/does-systemc-unit-testing-need-forking https://stackoverflow.com/questions/4923292/using-existing-unit-test-frameworks-with-systemc
  8. Here is an example of connecting serial port model to TCP socket: https://git.greensocs.com/models/tcp_serial
  9. Runs without any issues on Linux: 0 s s: true 0 s i: true 50 ms s: false ... 950 ms s: false Unfortunately I have no Windows machine near me to check with MSVC.
  10. Compiles without any warnings in G++4.8.
  11. Class Top is not declared/defined
  12. detect.h source code is not included, so I can't compile this.
  13. Unfortunately being a hardware developer you are doomed to suffer. You should either accept it, or quit :) EDA vendors assume that you will be using SystemC as a part of some commercial simulation or synthesis tool, and Red Hat 6 is the only supported platform in general.
  14. Yes, both are just C++ libraries.
  15. If you are using CMake build, then just pass -DBUILD_EXAMPLES=ON and all bundled examples will be built. Including risc_cpu example. You can run examples using general CTest flow (check documentation on cmake website https://cmake.org/Wiki/CMake/Testing_With_CTest )