Thursday, November 20, 2008     Register | Login | Search | Contact Us
     
   
     
     

Many of you already received communications about the move of the Cadence user community into cadence.com. And many of you have already joined, with over 4000 registrations in the first two weeks.

The new Cadence Community enhances the ability of Cadence users to connect and collaborate. In addition to moving the community into cadence.com -- enabling single sign-on for community, Sourcelink and Cadence events -- the new site is organized around nine technology segments, giving you easy access to product information, training, forums and blogs. Some of the new features include:
  • Ability to respond to posts via e-mail
  • Technology-specific blogs
  • Latest Web 2.0 social networking capabilities
  • Public profile options
  • Private messaging
  • Friends lists
Visit the new Cadence Community today at www.cadence.com/community and join the discussions!

Registration note: Due to the scope of the enhancements and the new SSO registration system, we were not able to migrate existing cdnusers.org member accounts. So new registrations are required, but this enables a broader set of functionality we think you'll enjoy.

Forum note: Under the guidance of forum moderators, we have taken the 20+ cdnusers.org forums and consolidated them into 11 forums on the new site. Posts have been brought over so you can leverage that posting history. CDNusers forums will be set to read only starting 7/30, and cdnusers.org will be redirected to the new community on 8/4.

Best regards,
Mike and Tom

Michael A. Catrambone - Steering Committee Chairman
Distinguished Engineer
PCB/Mechanical
UTStarcom, Inc.

Tom Diederich
Cadence Community Manager
Home
Forums
Forums > Digital IC > Formal verification

Subject: Resolving aborts after "analyze abort -compare"
Posting to forums is available to community members only.
Login or Register
Rate this topic:
   
Author Messages
blackj
Posts: 1
Online: User is Offline
1/22/2007 7:08 AM  
I am trying to compare RTL to netlist of a design and after mapping compare and analyze abort -compare I am still left with 46 aborts. If I try to analyze the abort again the tool crashes. If I diagnose the abort I get no error candiates, 3 diagnose point clock, reset and data. The corresponding supports are 3 primary inputs and the register the reset signal is coming from which is equivalent. I am working with the RTL designers to find places where I can add partition point but so for I haven't found any satisfactory one. The logic leading to these flops are quite large but nothing to complex really and the tool has been able to resolve similar flop on these registers. I.e. test_regΎ] is equivalent but test_regΏ] is an abort point. Has anybody encountered a problem similar to this and if so how was it resolved.
croy
Posts: 54
Online: User is Offline
2/05/2007 10:22 AM  
Hi

'analyze abort -compare' is definitely one of the first things to do when encountering aborts.

If you're using 6.2 and have access to an XL license (which it sounds like you do since you're using 'analyze abort') I would give 'add partition points -all' a shot next.

analyze datapath -verbose [maybe with -share and -effort high]

add partition points -all

add compared points -all

tclmode
foreach i "low high super" {
puts "// Info: running effort $i"
vpx set compare effort $i
vpx compare
vpx usage
}
vpxmode

Note that there's always the possibility you might get false failing points when using 'add partition points'. There's a way to deal with that situation so please let me know how it turns out.

If you still encounter aborts, consider sending Cadence the testcase. Actually, you should consider sending the testcase even if my little loop does the trick. R&D considers it a bug if 'analyze abort -compare' can't do what another command can.

Chrystian
Posting to forums is available to community members only.
Login or Register
Forums > Digital IC > Formal verification > Resolving aborts after "analyze abort -compare"


ActiveForums 3.6
     
Copyright 2006 Cadence Design Systems, Inc.