• 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. Autocorrection of ADE outputs in Assembler

Stats

  • Locked Locked
  • Replies 2
  • Subscribers 125
  • Views 4678
  • 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

Autocorrection of ADE outputs in Assembler

StephanWeber
StephanWeber over 1 year ago

Hi,

in newest versions I see that output becomes yellow if something goes wrong. However, for dependent expressions this works not so well:

vout VF(...)

f3dB bandwith(vout ...)

It seems the autocorrection works only fine, if I change one expression, then re-evaluate the output, and then change the next, re-eval, etc.

Is there a way to avoid these many re-evaluations?

Can I disable this checking feature for some edits?

I wonder, because it looks that this checking mechanism sometimes prevents edits which are fine, but just the system is not knowing this yet, without re-eval.

Bye Stephan

  • Cancel
  • Andrew Beckett
    Andrew Beckett over 1 year ago

    The "yellow" marking of outputs which have errors considered has been there for a little while (and there were some teething troubles with it initially). Which IC sub-version are you using (in case you're using a problematic version)?

    I don't know what you mean by "It seems the autocorrection works only fine..."? What "auto-correction" are you talking about?

    StephanWeber said:
    I wonder, because it looks that this checking mechanism sometimes prevents edits which are fine, but just the system is not knowing this yet, without re-eval.

    This might be the symptoms of the teething troubles I was referring to - I had a CCR "Erroneous yellow indication of invalid expression prevents editing of outputs" which was fixed in IC6.1.8/ICADVM20.1 ISR28 (strictly speaking the edits did happen, but there was a refresh problem on the screen which made it look as if they hadn't happened). So let me first check what sub-version you're using...

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • StephanWeber
    StephanWeber over 1 year ago in reply to Andrew Beckett

    Hi Andrew, I am using ICADVM20.1-64b.500.25. And I believe the CCR you mention can fit to my issue too. I can ask to switch to isr28.

    Bye Stephan

    • 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