Stats

  • Locked Locked
  • Replies 5
  • Subscribers 64
  • Views 13831
  • 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

forml verification on system level verification

archive

Hi all,

I would like to know if you are able to use the formal verification on the system level verification.


Thanks,


Originally posted in cdnusers.org by abna
Parents

  • Assuming you do a pretty good job of your block-level verification, then system verification is going to be (broadly) a mixture of integration testing and architectural verification. I say this because your block verification should have ensured that blocks behave perfectly when they receive valid inputs, and also that each block feeds valid inputs to its neighbours.

    Integration testing is asking "did I connect all the blocks correctly".
    For this we have a lot of success using IFV to prove the connections between IP blocks, and to the pads. It's pretty clear what should be tested, and IFV proves if there is any bad MUXing etc pretty fast. In fact we have a combination of Excel sheet and Perl script to do all the property writing for you. All you have to do is list the connection requirements.

    Architectural verification is making sure the blocks work in harmony to produce the desired system properties. E.g. "can I play MP3 files at all the supported bit rates".
    I can't see much scope for writing PSL / SVA properties for such high-level behaviour, so I would leave that to simulation with some directed or coverage-driven tests.

    Hope this helps.


    Originally posted in cdnusers.org by stephenh
Reply

  • Assuming you do a pretty good job of your block-level verification, then system verification is going to be (broadly) a mixture of integration testing and architectural verification. I say this because your block verification should have ensured that blocks behave perfectly when they receive valid inputs, and also that each block feeds valid inputs to its neighbours.

    Integration testing is asking "did I connect all the blocks correctly".
    For this we have a lot of success using IFV to prove the connections between IP blocks, and to the pads. It's pretty clear what should be tested, and IFV proves if there is any bad MUXing etc pretty fast. In fact we have a combination of Excel sheet and Perl script to do all the property writing for you. All you have to do is list the connection requirements.

    Architectural verification is making sure the blocks work in harmony to produce the desired system properties. E.g. "can I play MP3 files at all the supported bit rates".
    I can't see much scope for writing PSL / SVA properties for such high-level behaviour, so I would leave that to simulation with some directed or coverage-driven tests.

    Hope this helps.


    Originally posted in cdnusers.org by stephenh
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.