Stats

  • Locked Locked
  • Replies 1
  • Subscribers 91
  • Views 14870
  • 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

Max_tran violation not resolved in INNOVUS

Andrea Spiezia

Hi,

there is a way to know why INNOVUS optDesign -postroure is not able to solve a max_tran violation ?


  • Hi Andrea,
    with the following switch you can increase the verbosity of optDesign w.r.t. failing reasons for DRVs:
    setOptMode -detailDrvFailureReason true (CUI: set_db opt_detail_drv_failure_reason true)

    If you have many violated nets you might want to increase the maximum number of nets reported using this switch:
    setOptMode -detailDrvFailureReasonMaxNumNets 100 (CUI: set_db opt_detail_drv_failure_reason_max_num_nets 100)

    The reasons for the failing will be written in reports under timingReports/drvFailureReason.

    This is how the report for a net can look like this:

    Net 1: FE_PDN0_out_c                                     
    Viol: -0.2746
    MultiBuffering: Skipped due to DontTouch Net



    Dimo

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.