• 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. FSM coverage and generate block

Stats

  • Locked Locked
  • Replies 1
  • Subscribers 65
  • Views 14043
  • 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

FSM coverage and generate block

karlsmartin
karlsmartin over 16 years ago

Hi all,

I'm doing a coverage for a simple FSM. A generate block is analyzing the state of the FSM. The ICC is extracting the real FSM and one for every block in the generate statement. For example:

generate for (i=1; i<=12; i=i+1)
...
    if (state[i]) begin
        ...

This way I get 13 state machines extracted and only for the real one and the last block I get coverage data. This way my coverage is only 100 / (i+1) % of the real coverage.

Is there any possibility to get rid of this problem.


Regards,
martin

  • Cancel
  • StephenH
    StephenH over 16 years ago
    For the record, I've contacted Martin off-line to discuss the specifics of his design, but I thought I'd share a more generic comment with the forum at large.

    Design practices generally recommend to code FSMs in 1 or 2 processes; and the coverage algorithms in IUS identify FSMs based on these design templates.If you code the output logic using a generate loop, as Martin described, then each iteration of the loop creates a new process or always block. This is functionally correct but contravenes the 1-or-2-process guideline. This leads to the coverage system becoming confused about the user's intentions.

    One could almost certainly replace the generate loop with a single always block, which might be easier to read and would avoid the extra bit of hierarchy that a generate statement introduces.
    • 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