EDAboard.com | EDAboard.eu | EDAboard.de | EDAboard.co.uk | RTV forum PL | NewsGroups PL

Timing simulation error on bus

elektroda.net NewsGroups Forum Index - VHDL Language - Timing simulation error on bus

JSreeniv
Guest

Mon Dec 14, 2009 6:42 am   



Hi all,
I am running post route timing simulations for my modules where the
targeted device is Actel proasic3.
I had net list and sdf files for running these simulations.
When running for Min,Typ,Max simulations, i am getting the simulations
results on waveform for only Typ and Max but not for Min. For Min
simulation up to some steps are running and the output bus become idle
until the end of simulation time finishes.
I came to know that by adding 1 ps resolution time then it works,..so
i went for that by giving 1 ps at Modelsim vsim command line its
surprise to see the all results. I am happy but why it is happen for
the Min simulation only ..

Please anyone give some knowledge on this...why it happens

Thanks

KJ
Guest

Mon Dec 14, 2009 2:06 pm   



On Dec 13, 11:42 pm, JSreeniv <sreenivas.jyo...@gmail.com> wrote:

Quote:
I came to know that by adding 1 ps resolution time then it works,..so
i went for that by giving 1 ps at Modelsim vsim command line its
surprise to see the all results. I am happy but why it is happen for
the Min simulation only ..

Please anyone give some knowledge on this...why it happens


Presumably because the typ and max simulation models did not try to
delay anything by less than 1 ns but the min simulation did (assuming
that you previously had 1 ns time resolution).

KJ

JSreeniv
Guest

Mon Dec 14, 2009 5:26 pm   



On Dec 14, 5:06 pm, KJ <kkjenni...@sbcglobal.net> wrote:
Quote:
On Dec 13, 11:42 pm, JSreeniv <sreenivas.jyo...@gmail.com> wrote:

I came to know that by adding 1 ps resolution time then it works,..so
i went for that by giving 1 ps at Modelsim vsim command line its
surprise to see the all results. I am happy but why it is happen for
the Min simulation only ..

Please anyone give some knowledge on this...why it happens

Presumably because the typ and max simulation models did not try to
delay anything by less than 1 ns but the min simulation did (assuming
that you previously had 1 ns time resolution).

KJ

Hi KJ,
I am still not getting the reason why it happen, yes as from your
response my previous max and typ simulations are had 1 ns time
resolution.

Thanks

Kenn Heinrich
Guest

Mon Dec 14, 2009 7:38 pm   



JSreeniv <sreenivas.jyothi_at_gmail.com> writes:

Quote:
I am still not getting the reason why it happen, yes as from your
response my previous max and typ simulations are had 1 ns time
resolution.


In VHDL, if you specify a time less that the resolution limit, the
simulator turns that into zero time. That means that events which have
a proper ordering when executed with a 1 ps limit:

if rising_edge(clk)
a <= '1' after 100 ps; -- a happend after clk
b <= '0' after 200 ps; -- b happens later than a
end if;

will become equivalent to a system with totally different order

if rising_edge(clk)
a <= '1' after 0 ns;
b <= '0' after 0 ns; -- b,a both happen one delta cycle after clk
end if;

This usually messes things up pretty badly :-)

- Kenn

--
---------------------------------
Remove NOSPAM from email address.

elektroda.net NewsGroups Forum Index - VHDL Language - Timing simulation error on bus

Arabic versionBulgarian versionCatalan versionCzech versionDanish versionGerman versionGreek versionEnglish versionSpanish versionFinnish versionFrench versionHindi versionCroatian versionIndonesian versionItalian versionHebrew versionJapanese versionKorean versionLithuanian versionLatvian versionDutch versionNorwegian versionPolish versionPortuguese versionRomanian versionRussian versionSlovak versionSlovenian versionSerbian versionSwedish versionTagalog versionUkrainian versionVietnamese versionChinese version
RTV map EDAboard.com map News map EDAboard.eu map EDAboard.de map EDAboard.co.uk map Opony