Stats

  • Locked Locked
  • Replies 11
  • Subscribers 166
  • Views 20689
  • Members are here 0
More Content
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

Following up the subject of Cadence 16.6 and 17.2

TiBo

Hi all,

I am appreciate for all of your help. Since I am about to get cross over to the new 17.2 from 16.6

Do any of you have problem with the libraries, for example: Do you have any problem using lib created with 16.6 in 17.2 and via versa?

If you do, please let me know what I have to watch for? How smooth is the 17.2 software going so far?

Thank so much,

Regards,

TiBo

Parents
  • riklee
    16.6 symbols will uprev on the fly when using them in 17.2.
    17.2 is not(!) backward compatiable to 16.6. If you move a file to 17.2 you will not be able to open it with 16.6.

    To prevent any accidental saves of 16.6 data that may have been opened with 17.2 use the variable that was introduced with the 17.2 QIR1 (S004)release

    uprev_answer:
    If set, does not display the major release design uprev warning but provides the default answer. If value is "no" then a user is not able to open designs from older releases without using another method. This disables the noconfirm_uprev environment variable.
Reply
  • riklee
    16.6 symbols will uprev on the fly when using them in 17.2.
    17.2 is not(!) backward compatiable to 16.6. If you move a file to 17.2 you will not be able to open it with 16.6.

    To prevent any accidental saves of 16.6 data that may have been opened with 17.2 use the variable that was introduced with the 17.2 QIR1 (S004)release

    uprev_answer:
    If set, does not display the major release design uprev warning but provides the default answer. If value is "no" then a user is not able to open designs from older releases without using another method. This disables the noconfirm_uprev environment variable.
Children
No Data
Cadence Guidelines

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.