• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Functional Verification
  3. ifv: initialisation with init -load

Stats

  • Locked Locked
  • Replies 3
  • Subscribers 64
  • Views 1455
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

ifv: initialisation with init -load

archive
archive over 18 years ago

Hi,

I am trying to initialise my design with loading the waveforms from normal simulation because ifv is having difficulties with normal procedur (apply reset and run a few cycles)

I tried to load the waves but I don't have the syntax exactly right. Can anybody help?

My traces are in :

../nccoex/rundir_otb_ddrii/traces/

containing traces.dsn and traces.trn

When I open the traces with simvison the database is called traces::

I tried:

=>FormalVerifier> init -load -sst2 ../nccoex/rundir_otb_ddrii/traces -time 150ns

'1493' Signals not found in database, retaining old values for these signals.

formalverifier: Initial value of state variables loaded from SST2 database at time "1.5e-7s".

=>FormalVerifier> init -load -sst2 traces -root ../nccoex/rundir_otb_ddrii/traces -time 150ns

formalverifier: *E,SSDBER: Could not load database traces : No such file or directory.

=>FormalVerifier> init -load -sst2 ../nccoex/rundir_otb_ddrii/traces -root traces -time 150ns

formalverifier: *E,SSDBSC: Can not find top module "traces" in database ../nccoex/rundir_otb_ddrii/traces.

=>FormalVerifier> init -load -sst2 ../nccoex/rundir_otb_ddrii/traces -root traces::ip_pnx8542_2032lib.ip_pnx8542_2032_tb(testbench) -time 150ns

formalverifier: *E,SSDBSC: Can not find top module "traces::ip_pnx8542_2032lib.ip_pnx8542_2032_tb(testbench)" in database ../nccoex/rundir_otb_ddrii/traces.

If I do init -show the still all registers are 1'bx

Thanks,

Frank 


Originally posted in cdnusers.org by frank.vaneerdewegh
  • Cancel
Parents
  • archive
    archive over 18 years ago

    Hi Frank,

    you need to specify the root path to the toplevel, starting with ":" for the toplevel, e.g. if you have the following:

    Sim hierarchy: ip_pnx8542_2032_tb:dut
    IFV hierarchy: dut

    init -load -sst2 ../nccoex/rundir_otb_ddrii/traces -root [b]:dut[/b] -time 150ns

    What kind of issues are you facing with the Tcl initialization?

    Joerg.


    Originally posted in cdnusers.org by foster
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • archive
    archive over 18 years ago

    Hi Frank,

    you need to specify the root path to the toplevel, starting with ":" for the toplevel, e.g. if you have the following:

    Sim hierarchy: ip_pnx8542_2032_tb:dut
    IFV hierarchy: dut

    init -load -sst2 ../nccoex/rundir_otb_ddrii/traces -root [b]:dut[/b] -time 150ns

    What kind of issues are you facing with the Tcl initialization?

    Joerg.


    Originally posted in cdnusers.org by foster
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Children
No Data

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information