• 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. which all signals need to be initialized in a module

Stats

  • Locked Locked
  • Replies 2
  • Subscribers 64
  • Views 13402
  • 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

which all signals need to be initialized in a module

BharathECE
BharathECE over 12 years ago

Hi

 Iam doing formal verification,Iam getting so many signals unitialized.Iam not understanding which signals we should initialize.How to know which signals we should initialize in a module.

  • Cancel
  • CrazyForFormal
    CrazyForFormal over 12 years ago

    BharathECE,

    This is not a formal only question.  What does the designer or spec say about resetting the design?  If you are running simulation you have the same concerns.

    To initialize the design in IEV, use the tcl force commands to drive the reset signals to their appropriate values and then use the run command to run the clocks.

    clock -add clk 

    force reset_n 0
    # Run the reset for 5 clocks
    run 10
    # Load formal model with initialization state
    init -load -current
    # Display flop values
    init -show

    Hope this helps jumpstart you.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • BharathECE
    BharathECE over 12 years ago

    Hi

     Thanks for the reply,

     

    Its true this question was nothing related to IFV.Actually in any design we need to have some signals initialized as per design after reset process completed.

    That we can do by doing signal force. These things need to be discussed with designer of particular block/module.

     

    Thanks

    Bharath 

     

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel

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