Home
  • Products
  • Solutions
  • Support
  • Company

This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  • Products
  • Solutions
  • Support
  • Company
Community Verification IP Simvision debugging techniques

Stats

  • Locked Locked
  • Replies 0
  • Subscribers 12
  • Views 13407
  • 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

Simvision debugging techniques

MaheshKumar
MaheshKumar over 4 years ago

Hi All,

I am using simvision(64) 19.03.a001 version. 

I would like to more about debugging in simvision. 

1) .svcf (data base saving)

Lets say I ran one testcase and saved the Database as TEST1.svcf, which is a passing scenarios. 

I ran one more testcase which is TEST2, which is generally failing scenario. I will load this into simvision along with TEST1.svcf.  

Now in the waveform,  I have two databaes, one is passing one and one more is failing one.  

With this feature, will any difference shown by simvision to identify which signal has caused the fail or where is the exact issue by comparing. 

a) I just want to understand using .svcf can we compare data base of pass and fail so that easily we can point out the exact issue ?

b) Lets say we have 100 scenarios and it is difficult to have 100 .svcf's always. So, how can be this used in general way to that it can be re checked for 100 scenarios ?

Kindly advice for both a and b

2) .svwf (saving signals)

Hope this is just saving set of signals and it is independent of particular database. This we can use with any database. Please confirm

Thank You,

Mahesh

  • 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