Issue link: https://resources.pcb.cadence.com/i/1180190
Migration Guide for Allegro Platform Products Allegro Platform Front-End Products October 2019 14 Product Version 17.4-2019 © 1999-2019 All Rights Reserved. Preparing to Migrate Designs to the 16.5 Release To avoid any data loss and to ensure successful migration, perform the following actions sequentially on a pre-16.5 release design: 1. Ensure that design libraries for all the components which are used in the design are accessible. 2. Save the design hierarchy before migrating a pre-16.5 design to the 16.5 release. 3. Ensure that all non-sync constraints on the schematic are synchronized. The design is uprev-ed only after constraints are synchronized. You can sync constraints in either of the following ways: ❑ Choose Tools – Constraints – Synchronize in DE-HDL. ❑ Run the following command in batch mode to synchronize constraints: concept2cm -proj < .cpm > -export -forward -uprev 4. Launch Constraint Manager. If there are differential pairs on more than two nets that are part of Xnets, launching Constraint Manager ensures that there are no errors when upreving. 5. Synchronize the front-end design with the back-end design by running the export physical, netrev, and import physical operations. 6. Ensure that the design is not read-only, so that new files can be generated when the design is migrated to the 16.5 release. 7. Perform an ECset audit in Constraint Manager by selecting Tools – Audit Ecset. Steps to Migrate Designs to the 16.5 Release The following section describes the steps to uprev your design to the 16.5 release: 1. Open an existing design in 16.5.