Stats

  • Locked Locked
  • Replies 3
  • Subscribers 143
  • Views 1684
  • 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

filter out warn msg ( SCH -2162) symbol "***" has been updated since "***" schematic was last saved.

mlea

im trying to  avoid from output to CIW  these kind of warnings. Im running a skill script that recursivly filter down the hirarchy,

and each time the schematic data is newer than the symbol data  - i get these warn msg. and lot of them.

i tried the  few different approaches ( getWarn ) - none of them  was effective. i also did some reading and I do understand that the time stamp that used to be on previous IC version isn't being used today.

what is the correct method to completely get rid of this specific warn ? .

Thx

meny

  • Hi Meny,

    So how are you traversing the hierarchy? I'd only expect these messages to happen if you're opening them with the schematic editor - rather than using db functions. Are you opening the designs in readonly mode? If so, using:

    envSetVal("schematic" "readOnlyCheckEnabled" 'boolean nil)

    might stop it doing the check (I didn't test this - it's a holiday in the UK today so this is a very quick answer). If I knew more about what you're doing I could probably give a more directed answer.

    Worst case it ought to be possible to redirect the warnings - but I wanted to understand more about the approach you're taking before suggesting that.

    Regards,

    Andrew.

  • in reply to Andrew Beckett

    Hello Andrew,

    im using the db function: dbOpenCellViewByType()  to traverse through the hierarchy.

    but only NOW I see that the first recursive loop, which start from  the top of the design, using  cv= geGetEditCellView(). would that be a problem ?

     Im open the different hierarchies for read only mode.

    thx

    Meny

  • in reply to mlea

    Hi Meny,

    That's strange. Are you using any sch functions in your code? I can't see why it would complain otherwise...

    Using geGetEditCellView at the top level shouldn't cause this.

    Regards,

    Andrew.

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.