• 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. Failed to initialize incremental netlisting

Stats

  • Locked Locked
  • Replies 3
  • Subscribers 126
  • Views 21109
  • 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

Failed to initialize incremental netlisting

sjwprc
sjwprc over 6 years ago

Hello,

    The log content:

\o ERROR (OSSHNL-153): Failed to initialize incremental netlisting because the run directory contains
\o netlist data from the previous netlisting session which has a corrupt global
\o map structure file '/xxx/maestro/results/maestro/Interactive/1/xxx/netlist/ihnl/globalmap'. Remove the "ihnl" and "map" directories from the
\o current run directory and netlist again.
\o 
\o "ERROR (OSSHNL-512): Failed to generate netlist because incremental netlisting data from the previous session is corrupt or missing. Clean the run directory and netlist the entire design.\n"
\o End netlisting Mar 6 12:02:05 2019
\o ERROR (OSSHNL-514): Netlist generation failed because of the errors reported above. The netlist might not have been generated at all, or the generated netlist could be corrupt. Fix the reported errors and regenerate the netlist.
\o ...unsuccessful.

Failure description:

Maestro is mapped from adexl by "open with". Test_A is defined by config.  Simulation using adexl is fine. 

When run sim with Maestro (assembler), such incremental netlist problem happen. 

When define Test_A by schematic, no problem. 

I try to re-start cadence, remove history, not fix. 

Anyone has clue ?

BR

  • Cancel
  • Marc Heise
    Marc Heise over 6 years ago

    Hi,

    What IC version are you working with?  This may be fixed in a newer version. ( Help-> About Virtuoso)

    1. Try to do a complete re-netlist, not incremental  ( right mouse on test, netlist ..)

    2. Try to delete the simulation directory of the old run..or move it away if you want to keep it.

    Marc

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • ebecheto
    ebecheto 11 months ago

    Unfortunately, the thread  Failed to initialize incremental netlisting

    is locked, so i cannot answer to this. So i have to open a new discussion to answer to it.

    I had the same issue (probably using the same not up to date version of virtuoso)

    I passed through the issue by setting : Setup -> Job Setup -> Simulation -> Job Control Mode : ICRP

    it was checked LSCS : Large Scale Cloud Simulation 

    resulting in :

    ERROR (OSSHNL-153): Failed to initialize incremental netlisting because the run directory contains
    netlist data from the previous netlisting session which has a corrupt global
    map structure file '/tmp/.../maestro/results/maestro/ExplorerRun.0/.../netlist/ihnl/globalmap'. Remove the "ihnl" and "map" directories from the
    current run directory and netlist again.

    Hope it helps,

    May be we could allow unlock thread too ?

    No reason to lack a thread with one answer even if it is 6 years old

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett 11 months ago in reply to ebecheto

    We lock old threads for two reasons:

    1. This helps limit the opportunities for spammers to post junk on old threads
    2. It also helps reinforce the principle of keeping discussions separate for different topics (we have many cases where people used to post on old threads on a topic that was totally different).

    It's automated, so we can't really do it selectively. Having users able to unlock old threads would rather defeat the reasons above. Anyway, as moderator I unlocked the thread and joined your post to it. Note that in IC23.1 there's now an icon in a toolbar to clean up the tmp dir:

     

    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