Jump to content

Bas Arts

Members
  • Posts

    32
  • Joined

  • Last visited

  • Days Won

    1

Bas Arts last won the day on February 26 2019

Bas Arts had the most liked content!

2 Followers

Recent Profile Visitors

752 profile views

Bas Arts's Achievements

Advanced Member

Advanced Member (2/2)

4

Reputation

  1. Just out of curiosity: did you consider/discuss to use XML as a data modeling language i.s.o. JSON, for example to ease integration into or connection with IP-XACT?
  2. It is (typically) part of your vendor's tool installation. Inside the installation, look for "ubus" and/or "integrated". For example: $ find <path_to_vendor_installation> -name *ubus* If $UVM_HOME has been set correctly, you can also use $ find $UVM_HOME -name *ubus* Or simply use your favorite search engine on the web with terms "integrated", "ubus" and "uvm".
  3. Hi Sumit, I cannot test with gcc 9.3.0, but with SystemC 2.3.3 and gcc 9.1.0 using c++14 the following code doesn't give any problems: int sc_main(int argc, char* argv[]) { Blah myblah {"myblah"}; myblah.LetsWrite(); myblah.ThisOneFailsToo(); return 0; }
  4. It seems that you are mixing compiler versions and/or settings between the different packages you use. At least, your SystemC installation has not been built with the default GCC 4.8.5. Although not strictly necessary, I'd recommend to build SystemC, UVM-SystemC and SCV with the same compiler version and -options. I can confirm that with GCC 4.8.5, the SCV 'make check' also runs successfully.
  5. Hi Josep, After building SCV, did you run 'make check'? Did all tests pass? If so, could you share a small example that reproduces your problem? For me, 'make check' runs successfully using SystemC 2.3.3 and g++ 9.1.0. Thanks
  6. In addition, if your SystemC model contains ports of type double, you need to convert them in the test harness to 64 bit vectors first.
  7. On a side note, you might also consider moving to SystemC 2.3.3; SystemC 2.3.1 is fairly old.
  8. I guess the return value reflects either successful (zero) or non-successful (non-zero). E.g. the following code prints a non-zero value (in my case, 256 although I would have expected 1): module foo; int val; initial begin val = $system("test -f thisfileprobablydoesnotexist"); $display(val); end endmodule
  9. If you separate application code and read/write implementation code, you can keep your C code application and compile it still for your CPU module. Yes, you will need a C++ compiler then, but it also allows you to port your application to e.g. a commercial CPU model which could use plain C. You'd only need to replace your read/write C++ implementation with a C implementation. // C header file #ifndef C_H #define C_H #ifdef __cplusplus extern "C" { #endif /* __cplusplus */ void mywrite(uint32_t address, uint32_t value); void myread (uint32_t address, uint32_t *value); #ifdef __cplusplus } #endif /* __cplusplus */ #endif /* C_H */
  10. (See also https://github.com/OSCI-WG/uvm-core/issues/244) Functions last_req and last_rsp in uvm_sequencer_param_base.svh use "if (n == m_last_[req|rsp]_buffer.size())"; "==" should be replaced by ">=". Bas
  11. What errors do you get? From your question, it is not clear whether you have errors related to your (UVM-)SystemC installation, your Makefile, your application or something else.
  12. The freely available SCML library from Synopsys provides a way to describe registers with optional callback functions that will trigger when a register read or write occurs.
  13. Are you using a commercial simulator for your setup? Then consult its manual; but typically, you can use "-D<macro>[=<value>]" to define a macro.
  14. You could use an optional command line parameter to sc_main and propagate that to the "real" test.
×
×
  • Create New...