Jump to content


  • Posts

  • Joined

  • Last visited

Everything posted by Markus

  1. Hi, I'm trying to integrate SystemC into a software project in order to periodically simulate hardware parts. At the entry point of the simulation, I tried a minimalistic example: SC_MODULE(test){ SC_CTOR(test){}; }; test testObj("test"); sc_start(1, SC_US); // this is where the error occurs Ther error message is Error (E529) insert module failed runninIn file ../../src/sysc/kernel/sc_module_registry.cpp:47" thrown in the test body. I tried utilizing sc_main and played around with sc_elab_and_sim() a bit, but it doesn't seem to make a difference. Thanks in advance, Markus
  2. Hi Philipp, Thanks you very much for your answer! It already helped me, I simply tried it again and -voilà- a flawless installation procedure. Greetings from Zurich, Markus
  3. Hi maryam Let's start from the beginning... In the terminal, the command mv systemc-2.3.1.tgz systemc-2.3.1.tar will create a folder named systemc-2.3.1 in the same folder as tarball file is present. At systemc-2.3.1/src/sysc/datatypes/bit there should be a file named sc_bit_proxies.h which contains the keyword mutable. It specifies that the member which follows does not affect the externally visible state of the class - this led to linking problems in my first attempt. Therefore, all the occurrences of mutable should be deleted. To install the package, the bash can be used again: cd systemc-2.3.1 sudo mkdir /usr/local/systemc-2.3 mkdir objdir cd objdir sudo ../configure prefix=/usr/local/systemc-2.3 sudo make sudo make install Optionally, the rather long path to the packet’s location can be exported into an environment variable: export SYSTEMC_HOME=/usr/local/systemc-2.3/ To make the changes permanent, the environment file has to be edited: sudo gedit /etc/environment SYSTEMC_HOME=/usr/local/systemc-2.3/ Lastly the path in LD_LIBRARY_PATH needs to be updated: export LD_LIBRARY_PATH=/usr/local/systemc-2.3/lib-linux64:$LD_LIBRARY_PATH Regards, Markus
  4. Hi, I'm trying to integrate SystemC into a software project compiling with MinGW/gcc in order to periodically simulate hardware parts . However, linking the software with SystemC libraries (built with VS) leads to what I expect to be compiler interoperability artefacts like: Warning: corrupt .drectve at end of def file Targets\lib\SystemC.lib(Debug/sc_main_main.obj).text$mn+0x2e): undefined reference to `__security_cookie' Building the libraries with MinGW fails at the configure-step, as discussed in other topics. Is there any other way? Thanks in advance! -Markus
  • Create New...