• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Digital Implementation
  3. FGC adding MinMax Voltage panic!

Stats

  • Locked Locked
  • Replies 4
  • Subscribers 92
  • Views 13830
  • 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

FGC adding MinMax Voltage panic!

fitz
fitz over 8 years ago

I keep getting the 'subject' message during place_opt_design on a simple 28nm design.

Should I really panic?  ... OR  ... Is the placer recognizing a potential IR problem and  automatically correcting the issue?

New one for me ...  innovus v16.13-s045_1 .

Shawn

 

  • Cancel
  • Kari
    Kari over 8 years ago
    what is the message?
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Arkady7
    Arkady7 over 8 years ago
    Dear Fitz, Kari,

    I have got the same error message of "FGC adding MinMax Voltage panic!" numerous times during placement, CTS and routing.
    I am also using 28nm and Innovus v16.13.
    Do you have more information on this message?
    How critical is it?
    It is neither a warning nor an error message and there is no documentation on that.

    Thank you
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • fitz
    fitz over 8 years ago

    Charlotte:

    Sorry, I had no response from either STM or Cadence local.

    My specialty is genus >  innovus floorplaning preCTS ,  not gds out ,  so fortunately I was able to ignored the panic!

    You on the other hand have some research to do.

    Start with Kari : ) and then poke STM.

    Shawn

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Kari
    Kari over 8 years ago
    Don't Panic! :-)

    from what i can tell, this message was some extra debugging info that should not have been getting printed out to the log. it seems to be fixed in 16.20. So I think you can ignore it.
    • Cancel
    • Vote Up 0 Vote Down
    • 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