• 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. Custom IC Design
  3. 'layerHeader in update mode' assura error

Stats

  • Locked Locked
  • Replies 3
  • Subscribers 125
  • Views 648
  • 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

'layerHeader in update mode' assura error

loboveena
loboveena over 9 years ago

Hi

I get the following error while running Assura DRC ; Can you help me understand what this error means and how do I fix this ?

Assura version used : 4.1_USR4_HF24

-------------------------------------------------------------

Finished output post-processing
cpu: 0.14  elap: 0  pf: 0  in: 32  out: 440  virt: 135M  phys: 684M

*ERROR* layerHeader in update mode: group 754, layer 262043


*WARNING* aveng exit with bad status
*WARNING* Status 256
*WARNING* Assura execution terminated
--------------------------------------------------------------------------------------

Thanks,

Veena

  • Cancel
  • Andrew Beckett
    Andrew Beckett over 9 years ago

    Hi Veena,

    Please contact customer support. I can only find references to this error in very old versions of Assura (long before the one that  you're using) and those were supposedly fixed - so it must be due to something else.

    Kind Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • loboveena
    loboveena over 9 years ago

    Hi Andrew, 

    Can you atleast give me a hint regarding what this error means ?

    Thanks,

    Veena

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 9 years ago

    Hi Veena,

    The internal CCRs covering this don't really give any details - and they were fixed something like 7 years ago.

    So there's not much I can help you with here - which is why I suggested contacting customer support. Presumably you have something that reproduces the problem.

    Regards,

    Andrew.

    • 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