
enchanter
Members-
Content Count
48 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Calendar
Everything posted by enchanter
-
When I play around with the factory/basic example from uvm-systemc-1.0-beta1, In the original example code, it prints the instance override information as below: UVM_INFO @ 0 s: reporter [RNTST] Running test ... UVM_INFO ../../../../src/uvmsc/factory/uvm_default_factory.cpp(1185) @ 0 s: reporter [UVM/FACTORY/PRINT] #### Print Factory Configuration (*) Instance Overrides: Requested Type Override Path Override Type -------------- ------------- ------------- gen top.e.gen1 mygen Type Overrides: Requested Type Override Type -------------- -------------
-
I am try to compile tlm1/bidir example from uvm-systemc-1.0-beta1 with SystemC 2.3.2 I got error as below and I have no idea what I have done wrong. ~/systemc/include/tlm_core/tlm_1/tlm_req_rsp/tlm_channels/tlm_req_rsp_channels/tlm_put_get_imp.h:87:7: error: inherited virtual base class 'sc_core::sc_interface' has private destructor class tlm_master_imp : ^ I have attached the full compile log comp.log
-
Build issues with UVM-SystemC 1.0-beta1
enchanter replied to hle's topic in SystemC Verification (UVM-SystemC, SCV)
For the build issue, I think you can over CMake configure in SystemC to set library path to wherever you want. -
UVM-SystemC 1.0-beta1 Released
enchanter replied to Lynn Garibaldi's topic in SystemC Verification (UVM-SystemC, SCV)
Any plan to fix this build error on Mac OS? libtool: link: ar cru .libs/libmacros.a ar: no archive members specified usage: ar -d [-TLsv] archive file ... ar -m [-TLsv] archive file ... ar -m [-abiTLsv] position archive file ... ar -p [-TLsv] archive [file ...] ar -q [-cTLsv] archive file ... ar -r [-cuTLsv] archive file ... ar -r [-abciuTLsv] position archive file ... ar -t [-TLsv] archive [file ...] ar -x [-ouTLsv] archive [file ...] make[4]: [libmacros.la] Error 1 (ignored) -
UVM-SystemC 1.0-beta1 Released
enchanter replied to Lynn Garibaldi's topic in SystemC Verification (UVM-SystemC, SCV)
In installed uvm-systemc.pc file, it sets Libs to "-luvm". Should it be "-luvm-systemc"? -
Thanks for the help. I did some digging too and I also thought it is becaused by the clock events. So I tried to use the set_timeout on that example which should finished in 100 NS. When I set the timeout to 30 NS, it killed the simulation at 30 NS as expected. But when I set it to 200 NS, the simulation will not finish. I haven't figure out why.
-
I can't find any example in the uvm-systemc preview package which DUT has clock and reset signals. I tried to create clock with sc_clock in sc_main and connected it my dut's clock signal. But it looks the simulation will never finish. So would someone let me know what's the right way to handle the clock and reset signals?
-
I am learning the TLM example at_4_phase in the SystemC 2.3.1 package. But I don't know why there are 16 WRITE commands are generated by the traffic_generator? From my understanding, the m_transaction_queue is enqueue-ed twice. So I think it should only generate 2 commands then the queue should be empty. Why it generate 16 WRITE and 16 READ commands instread?
-
b-transport interface
enchanter replied to Reza_sh's topic in SystemC TLM (Transaction-level Modeling)
What's the local time for target when it received b_transport call, 1000ns or 1010ns? the target executes b_transport(tx, t), in which, t should be 100ns or 110ns? -
Read some examples about TLM and find the calls about "b_transport" with delay. But all of them just ignore it in the implementation. The sc_time_stamp() from both initiator and target are the same value in the print message. So I am not sure what's the "delay" should be used? I should wait for "delay" time to start processing request or process the request as soon as possible with my "processing delay" then wait for "delay" time or something else? Thanks.
-
I try to find a simple template which can compile both the example code and my own (in the future). The reason why I want one for the example code is I may try to do some modification on the example code to try things, it is too hard for me to tweak the original Makefile in the package. About the command line, I think that is not a good idea. There's so many flags you have to remember for just compile a single file. I consider Makefile is more productive.
-
I start to learn SystemC and SCV. But I don't have much experience on complex Makefile as the one provided in the install package by SCV. It is too hard for me to understand who the files are really compiled. I am not sure if any one can provide simple Makefile template (Only Linux platform is OK). Thanks.
-
I have a dynamic array in sequence item as below: rand int array_size; rand int a []; constraint c_order {solve array_size before a;}; constraint c_size { a.size() == array_size;}; In some tests, I hope to only create the array according to the randomized value of array_size but not do randomize on the value of it. Is there any way I can do that?
-
I try to define a sc_vector like this in SC_MODULE sc_vector<sc_signal<sc_uint<C_WIDTH> > > sDin("sDin", C_SIZE); Then I got this error: expected identifier before string constant sc_vector<sc_signal<sc_uint<C_WIDTH> > > sDin("sDin", C_SIZE); ^ I am not sure what is missing from there.
-
I am using QuestaSim 10.3a_1 and try to record a dynamic array in the sequence item. But it doesn't show in the waveform window. When I try to fix the array size and use uvm_field_sarray_int to record it, it works well and data show as expected in the waveform windows. My code: # sequence item parameter int P_BIT_DEPTH = 10; rand int unsigned data_len; rand bit unsigned [P_BIT_DEPTH-1:0] data []; ... `uvm_field_array_int(data, UVM_ALL_ON+UVM_UNSIGNED) `uvm_field_int (data_len, UVM_ALL_ON+UVM_UNSIGNED) ... constraint
- 1 reply
-
- uvm_field_array_int
- dynamic array
-
(and 3 more)
Tagged with:
-
How to pass modified Template argument to sub module?
enchanter replied to enchanter's topic in SystemC Language
Hi Philipp: Thanks for your clear explanation. -
I don't think OSCI gets synthesis feature to translate SystemC code to any level of schematic.