Has anyone ever been able to get Modelsim to model transport delays in Verilog? Verilog simulators, by default, use inertial delays, so if you have an assignment such as this:
assign #4 sig_out = sig_in;
then any pulse on sig_in that is less than 4ns will get swallowed. Modeling transport delays prevents this from happening. Modelsim claims to model transport delays using the +transport_int_delay option for vsim, but this just doesn't seems to work.
-Kevin
I think you'll find that this option applies only to interconnect delays that have been backannotated from an SDF file. The Verilog language defines continuous driver delays and net delays to be inertial, and I was under the impression that simulators aren't supposed to disobey that.
If you want transport delay in your own Verilog model, use intra-assignment nonblocking delays - try tnis...
always @(sig_in) sig_out
That is wonderful. It totally works. I wish I'd known this before. My Palnitkar book makes no reference to this (unsurprisingly) that I can see though I did find a reference in a book by Bhasker. I would like to be able to adjust the delay on-the-fly, in order to model pad/trace delays that change over time, but I don't think that's possible. I suppose maybe I could get a switchable delay doing something like this:
always@(sig_in, dly_sel) sig_out
Lots of people say that when we tell them :-)
It can do other magic too. The #N transport delay can be replaced with an event control:
sig_out be able to adjust the delay on-the-fly, in order to model pad/trace
It's panto time... Oh yes it is!!!!
The numeric value in the delay expression is evaluated each time the statement executes; it can be any run-time expression, unlike the delay in a continuous assign which must be an elaboration-time constant. The only thing to note is that any expression needs to be enclosed in parentheses. So...
sig_out
This is great stuff. I replaced all of my adjustable delay lines, which consisted of long shift registers clocked by a 10GHz clock so I could achive 100ps resolution. This was slowing down the simulation drastically. I guess it is panto time--whatever that might be. -Kevin
Sorry, I should have taken note of your timezone.
Someone else please explain :-)
-- Jonathan Bromley, Consultant
DOULOS - Developing Design Know-how VHDL * Verilog * SystemC * e * Perl * Tcl/Tk * Project Services
Doulos Ltd., 22 Market Place, Ringwood, BH24 1AW, UK snipped-for-privacy@MYCOMPANY.com
The contents of this message may contain personal views which are not the views of Doulos Ltd., unless specifically stated.
Perhaps this will help....
Or maybe not!
- Brian
Have something to add? Share your thoughts — no account required.
Ask the community — no account required