- 易迪拓培训,专注于微波、射频、天线设计工程师的培养
Preparing for the 17.0 Release
录入：edatop.com 点击：
在帮组里看到的！
------------------------------------------------------------------------------------
Preparing for the 17.0 Release
This release (16.6) will be the last version that will allow designs (boards, mcm, symbols and padstacks) created in releases earlier then 11.0 to be upreved to the current release. For these old design versions, you must have an OS (Sparc Solaris or AIX) with a Cadence Allegro install to successfully perform a uprev of designs older than 11.0. With 17.0, Cadence will still be able to uprev these old customer designs but even this capability will be discontinued when 16.6 is EOL.
As part of 17.0 adoption, if you have pre-11.0 designs you may need to access, you should either:
Uprev these designs to16.0 if you plan to have a need to continue to access them.
Provision a legacy system (Sparc or AIX) with 16.6 and preserve it as a uprev system.
Tips:
The batch program, dbstat, can be used to report the version of any Allegro database. It supports wildcards so it can be used to report the version of all databases in one directory.
The batch programs, uprev and uprev_overwrite, can be used to bring databases up to the current Allegro software version. They both support a recursion option (see documentation) that allows them descend a directory hierarchy, updating any Allegro designs found.
None of the these batch programs requires a Cadence license.
------------------------------------------------------------------------------------
Preparing for the 17.0 Release
This release (16.6) will be the last version that will allow designs (boards, mcm, symbols and padstacks) created in releases earlier then 11.0 to be upreved to the current release. For these old design versions, you must have an OS (Sparc Solaris or AIX) with a Cadence Allegro install to successfully perform a uprev of designs older than 11.0. With 17.0, Cadence will still be able to uprev these old customer designs but even this capability will be discontinued when 16.6 is EOL.
As part of 17.0 adoption, if you have pre-11.0 designs you may need to access, you should either:
Uprev these designs to16.0 if you plan to have a need to continue to access them.
Provision a legacy system (Sparc or AIX) with 16.6 and preserve it as a uprev system.
Tips:
The batch program, dbstat, can be used to report the version of any Allegro database. It supports wildcards so it can be used to report the version of all databases in one directory.
The batch programs, uprev and uprev_overwrite, can be used to bring databases up to the current Allegro software version. They both support a recursion option (see documentation) that allows them descend a directory hierarchy, updating any Allegro designs found.
None of the these batch programs requires a Cadence license.
提供一些更改内容的消息呗，或者时间表也行。
Thanks for infor ！
看看
