V
vijayakumar
Guest
please can explain the transport delay in vhdl?
what difference between inertial delay and transport delays?
what difference between inertial delay and transport delays?
Navigation
Install the app
How to install the app on iOS
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
More options
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
K
KJ
Guest
On Mar 8, 5:14 am, "vijayakumar" <regupathivijayaku...@gmail.com>
wrote:
signals 'b' and 'c'.
a <= '0, '1' after 10 ns, '0' after 11 ns;
b <= a after 20 ns;
c <= transport a after 20 ns;
Siganls 'b' and 'c' both model a 20 ns delay line where the output is
intended to follow the input signal 'a' (just 20 ns later). What
you'll see is that signal 'c' looks just like 'a' but shifted over by
20 ns but signal 'b' will show no activity until t=31 ns at which time
it will change from 'U' to '0', never having gone to a '1'.
The reason for this is the difference between 'inertial' and
'transport' delays. If you'll notice, signal 'a' is simply a 1 ns
wide pulse which happens to be less than the 20 ns of 'inertial'
delay. When multiple events happen on a signal within the inertial
delay interval, all but the last event is basically discarded. If you
changed a to generate 50 ns wide pulse (or anything greater than 20
ns) then signals 'b' and 'c' will both behave in the same manner and
will model what you would think a 20 ns delay line should be doing.
Depending on what you're modelling, both forms can be useful. For
synthesis, delays are not supported.
Kevin Jennings
wrote:
Try simulating the following code and look at the differences betweenplease can explain the transport delay in vhdl?
what difference between inertial delay and transport delays?
signals 'b' and 'c'.
a <= '0, '1' after 10 ns, '0' after 11 ns;
b <= a after 20 ns;
c <= transport a after 20 ns;
Siganls 'b' and 'c' both model a 20 ns delay line where the output is
intended to follow the input signal 'a' (just 20 ns later). What
you'll see is that signal 'c' looks just like 'a' but shifted over by
20 ns but signal 'b' will show no activity until t=31 ns at which time
it will change from 'U' to '0', never having gone to a '1'.
The reason for this is the difference between 'inertial' and
'transport' delays. If you'll notice, signal 'a' is simply a 1 ns
wide pulse which happens to be less than the 20 ns of 'inertial'
delay. When multiple events happen on a signal within the inertial
delay interval, all but the last event is basically discarded. If you
changed a to generate 50 ns wide pulse (or anything greater than 20
ns) then signals 'b' and 'c' will both behave in the same manner and
will model what you would think a 20 ns delay line should be doing.
Depending on what you're modelling, both forms can be useful. For
synthesis, delays are not supported.
Kevin Jennings