Answers Database Design Manager/Template Manager M1.5: Flow Engine reads incorrect settings if a default template is customized Record #4252 Product Family: Software Product Line: M1 Graphical/General Product Part: Design Manager Product Version: 1.5is2 Problem Title: Design Manager/Template Manager M1.5: Flow Engine reads incorrect settings if a default template is customized Problem Description: Urgency: Standard The following scenario can produce this issue: 1. Select Utilities->Template Manager from the Design Manager 2. Within the TM, select the Customize button for the Default Template 3. Enter in certain program/options, for example: ngdbuild: -nt on map: -l -k par: -s 4. Click on 'Set' to set the options, then OK to save 5. Now create a new template by selecting the 'New' button 6. Give your new template a name 7. Select the Customize button for this new template. 8. Enter in certain program/options, for example: map: -u par: -y trce: -a -b 9. Click on 'Set' to set the options, then OK to save 10. Select 'Close' to shut down the Template Manager 11. Select Design->Implement->Options from within DM to open the Options dialog 12. Select your newly created template (and not the default customized template) from the pull-down menu under the appropriate Program Option Template. 13. Select OK to save, then 'Run' to begin executing the implementation Pay particular attention to the command line options executed (Utilities-> Command History->Command Line). You will notice that the customized options we set for the Default Template are run in addition to those options specified within our user-defined template. Following the example above, the resulting commands would be: ngdbuild: -nt on // from default map: -u // from user-defined overriding default par: -y // from user-defined overriding default trce: -a -b // from user-defined Where applicable, the options specified in the user-defined template overide the same program options specified in the default customized template. Solution 1: This is a known issue in M1.5 The problem is a result of customizing the default template from within the Template Manager. This issue will be addressed in a future release. WORKAROUND: Do not customize a default template from within the Template Manager. As long as a program/option is defined for a newly created template, and that template is selected in the options dialog, it will be implemented properly. End of Record #4252 - Last Modified: 11/10/98 11:49

For the latest news, design tips, and patch information on the Xilinx design environment, check out the Technical Tips!