unsupported feature: event controls
iverilog -y. -I.. -Wall -DICARUS -DSIMULATION -mfileio -DVCD -y
model -I config -o k4s643233h_0401 k4s643233h_0401.v -M
k4s643233h_0401.deps
k4s643233h_0401.v:800: sorry: Event controls not supported here.
k4s643233h_0401.v:802: sorry: Event controls not supported here.
k4s643233h_0401.v:811: sorry: Event controls not supported here.
k4s643233h_0401.v:951: sorry: Event controls not supported here.
k4s643233h_0401.v:974: sorry: Event controls not supported here.
k4s643233h_0401.v:977: sorry: Event controls not supported here.
k4s643233h_0401.v:1296: sorry: Event controls not supported
here.
k4s643233h_0401.v:1326: sorry: Event controls not supported
here.
k4s643233h_0401.v:1775: sorry: Event controls not supported
here.
k4s643233h_0401.v:1913: sorry: Event controls not supported
here.
k4s643233h_0401.v:1914: sorry: Event controls not supported
here.
k4s643233h_0401.v:1919: sorry: Event controls not supported
here.
k4s643233h_0401.v:2018: sorry: Event controls not supported
here.
k4s643233h_0401.v:2021: sorry: Event controls not supported
here.
k4s643233h_0401.v:2024: sorry: Event controls not supported
here.
k4s643233h_0401.v:2030: sorry: Event controls not supported
here.
k4s643233h_0401.v:2566: sorry: repeat event control not
supported.
k4s643233h_0401.v:2570: sorry: repeat event control not
supported.
make: *** [k4s643233h_0401] Fehler 18
line 800 and 802 are the "data_read <= ...." lines
always @(READ_MODE) begin
// data_read <= repeat(CL-1) @(posedge pclk) READ_MODE;
// VCS does not support above statement. However Verilog-XL is
OK.
// So, I modified as following statement for VCS.
#0.1;
if (READ_MODE == 1'b1)
data_read <= repeat(CL-1) @(posedge pclk) 1'b1;
else
data_read <= repeat(CL-1) @(posedge pclk) 1'b0;
end
don't even properly understand what this does, I only wanted to
use the SDRAM model for verification.
Nobody/Anonymous
2005-10-11
SDRAM model (c) SAMSUNG (from their web)
Stephen Williams
2006-10-01
Cary R.
2007-11-14
Logged In: YES
user_id=1651735
Originator: NO
Fixing this should also fix always3.1.1K.v, always3.1.2G.v, always3.1.2H.v and always 3.1.2I.v.
Cary R.
2008-08-22
Cary R.
2008-09-03
Logged In: YES
user_id=1651735
Originator: NO
I'm looking into this. I have repeat working for blocking statements, but the non-blocking statements require changes to both the compiler and the run time.
Cary R.
2008-09-03
Cary R.
2008-09-11
This is not fix yet. I don't have non-blocking assignments working for bit based values, but it is working well enough that I have uncovered a different problem. There are continuous assignments that are getting their delay from a variable and Icarus does not support this. Once I finish the non-blocking event delays I will fix the delay problem. It appears to be as simple as using the variable delay operator instead of the fixed delay operator in the code generator.
Cary R.
2008-09-12
FYI I have submitted a patch for the variable delay problem.
Cary R.
2008-09-18
Cary R.
2008-09-18
I have submitted a patch that allows the attached code to compile correctly. It appear that not enough code was supplied to actually run the memory model, but I have built test code to exercise vector and parts of a vector non-blocking event control. I have not finished adding this functionality for arrays, but that will happen soon and is not needed for this report, so I will close it.