Stats

  • Locked Locked
  • Replies 1
  • Subscribers 61
  • Views 2612
  • 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

Resolving aborts after "analyze abort -compare"

archive

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[0] is equivalent but test_reg[1] is an abort point. Has anybody encountered a problem similar to this and if so how was it resolved.


Originally posted in cdnusers.org by blackj
Parents

  • 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


    Originally posted in cdnusers.org by croy
Reply

  • 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


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