SysWip

i had to comment out this.constraint_mode(0) to avoid the crash with ncvlog

/////////////////////////////////////////////////////////////////////////////
/*- setRndDelay(): Enable random delays and set random constraints.*/
/////////////////////////////////////////////////////////////////////////////
task setRndDelay(int t_max, rndLevel);
this.t_max = t_max;
this.rndLevel = rndLevel;
this.c_timing.constraint_mode(1);
//MS this.rand_mode(1);
endtask
/////////////////////////////////////////////////////////////////////////////
/*- setTiming(): Set I2C bus custom timing.*/
/////////////////////////////////////////////////////////////////////////////
task setTiming(time t_Low, t_High, t_HoldStart, t_SetupStart,
t_HoldData, t_SetupData, t_Buff, t_Valid, t_SetupStop);
//MS this.rand_mode(0);
//MS this.constraint_mode(0);
this.t_Low = t_Low;
this.t_High = t_High;
this.t_HoldStart = t_HoldStart;
this.t_SetupStart = t_SetupStart;
this.t_HoldData = t_HoldData;
this.t_SetupData = t_SetupData;
this.t_Buff = t_Buff;
this.t_Valid = t_Valid;
this.t_SetupStop = t_SetupStop;
endtask

i then get the following errors due to the expected type of 2nd param of weiteData

—————————————————————————–
this.writeData({6′b011110, address[9:8]}, {address[7:0]}, 0);
|
ncvlog: *E,TYCMPAT (…/i2c_vip/verification_ip/master/i2c_m.sv,475|48): formal and actual do not have assignment compatible data types (expecting datatype compatible with ‘queue of bit8′ but found ‘logic’ instead).
—————————————————————————–
this.writeData(7′d0, {8′h06});
|
ncvlog: *E,TYCMPAT (…./i2c_vip/verification_ip/master/i2c_m.sv,513|25): formal and actual do not have assignment compatible data types (expecting datatype compatible with ‘queue of bit8′ but found ‘packed array’ instead).

package tbench.I2C_M
errors: 2, warnings: 0

hope parsing with ncvlog help to improve you VIP

regards

thanks tiksan
i’ll try to make the IP up and running with ncvolog. do you expect it will work if i comment out the rand_mode(1/0) statements?

what is of concvern is the other errors (TYCMPAT) which lead me to suppose ncvlog makes a stricter control on types than VCS, maybe hiding a real issue

i’ll let you know what my findings are (i am a SV starter, though)

thanks anyway for your great (and oper source) job!

Thanks a lot!

one more IUS compile issue i found in the program test

I2C_m_env i2c_m = new(i2c_ifc_m, “Standart”);
|
ncvlog: *E,VARIST (…/rests/RX_ISM_test.v,23|20): Local static variable with initializer requires ’static’ keyword.

This fix the problem
static I2C_m_env i2c_m = new(i2c_ifc_m, “Standart”);

regards

hello tiksan
a happy new year first!

your suggestion works fine

a quick question

what is underneath this conditional compile of the mailbox?

`ifdef VCS
typedef mailbox TransMBox;
`else
typedef mailbox #(I2C_m_busTrans) TransMBox;
`endif
i am trying both with IUS simulator

i am now trying the VIP at run time and it doesn’t work so i am investigating here

i feel the issue i am experiencing is in the put stament of the write function

this.trInBox.put(this.tr);

which cannot trigger a write transcation

i’ll keep you posted

hello tiksan
quick question, more related to system verilog methodology. what about using multiple test program? i.e. istantiating two programs
T1_test u_RX_ISM_test(.i2c_ifc_m(i2c_m_if_0));
T2_test u_DONKEY_test(.i2c_ifc_m(i2c_m_if_0));
in the exampletest bench?
my concern is that the every program create a new I2CM object which never get destroyed (so i may run in unefficient memory usage in case of MANY tests)
thanks much

hello tiksan
i need a hint from you: how can i make shure a write has been completed over the I2C bus without monitoring a stop condition inside the I2C slave? i actually use a signal in my unit under test which i poll until a stop is detected. is there a way to get the same from your BFM?
many thanks