Forum Discussion
Altera_Forum
Honored Contributor
11 years agoIt's a bit hard to recall this problem after almost two years. But as far as I can remember, read delay occured in Verilog simulations only on the first cycle. Other reads were identical in VHDL and Verilog. (If the delay is caused by registered output then the one-cycle delay will exist every cycle). Also "leds" is not an M4K port, it's top level design port.
There are new VHDL and Verilog simulation results attached. Also, there are new TCL-commands for ModelSim. VHDL:vlib workvmap work workvcom -reportprogress 300 -work work test_mem.vho
vsim -L cycloneii -voptargs=+acc -t ns work.test_mem
add wave -position end sim:/test_mem/clk
add wave -position end sim:/test_mem/address
add wave -position end sim:/test_mem/leds
force -freeze sim:/test_mem/clk 0 0, 1 {20 ns} -r 40ns
force -freeze sim:/test_mem/address 00000000 0
run 80ns
force -freeze sim:/test_mem/address 00000001 80ns
run 200ns Verilog: vlib workvmap work workvlog -reportprogress 300 -work work test_mem.vo
vsim -L cycloneii_ver -voptargs=+acc -t ns work.test_mem
add wave -position end sim:/test_mem/clk
add wave -position end sim:/test_mem/address
add wave -position end sim:/test_mem/leds
force -freeze sim:/test_mem/clk 0 0, 1 {20 ns} -r 40ns
force -freeze sim:/test_mem/address 00000000 0
run 80ns
force -freeze sim:/test_mem/address 00000001 80ns
run 200ns