Altera Home Page
Literature Licensing
Buy On-Line Download

  Home   |   Products   |   Support   |   End Markets   |   Technology Center   |   Education & Events   |   Corporate   |   Buy On-Line  
  Knowledge Database   |   Devices   |   Design Software   |   Intellectual Property   |   Reference Designs   |   Design Examples   |   mySupport  

 Products
   Quartus II
      SOPC Builder
      MAX+PLUS II
      ModelSim-Altera
  
 Resource Centers
      Overview
      Installation & Licensing
      Scripting
      Board Design & I/O
      Design Entry & Planning
      Synthesis & Netlist Viewers
      Incremental Compilation
      Optimization
      Power Management
   TimeQuest Timing Analyzer
      Classic Timing Analyzer
      Simulation & Verification
      On-Chip Debugging
      HardCopy Design
  
 Software Resources
      OS Support
      Driver Installation
  
 Download & Licensing
      Download
   Licensing
  
 Quartus II EDA Support
      Quartus II Interface
   Synthesis Tools
   Simulation Tools
   Formal Verification Tools
   Timing Analysis Tools
   Physical Synthesis Tools
   Board Level Tools
  
 Legacy Sw. EDA Support
      View by Vendor
      View by Tool
      View by Function
  

Upgrading Your Component with SOPC Builder Component Editor Version 7.2 and Later

Migrating older components built with the component editor in SOPC Builder version 6.1 and earlier (PTF based) to SOPC Builder version 7.2 component tcl-based format can be done with the component editor.

Using older components that use a PTF file to describe the component in SOPC Builder is supported, however the component’s GUI interface will run slower when SOPC Builder in running in compatibility mode to use the older component description files. Typically, you will see a slow down of the GUI interface when you add, edit, or move your component in the system.   

The new tcl-based component description file (<component_name>_hw.tcl) can improve the graphical tool performance when adding or editing a component in SOPC Builder and no changes are required to your HDL or software driver files. Only the component description file has changed from class.ptf to tcl.

There are two ways of using component editor to port your SOPC Builder component description to the new tcl-based component format with no changes to your HDL or software driver files.

Directly Open the Component Description File from the Component Editor

  • In the component editor, use Open dialog box from the File menu to select the component’s class.ptf file
  • The component class.ptf file, if created by a previous version of the component editor, will port the component description information into the tcl file format
  • Review the component settings in each tab to make sure the settings have ported correctly
  • In the Component Wizard tab, the component version number has been updated with a higher version number (from x.y to x.y.1)
  • Save your new component description file by clicking Finish
    • A new <component_name>_hw.tcl file is created for your component in the component directory
  • In SOPC Builder, refresh the component list by going to the Refresh Component List in the File menu to update your list of components. The updated component file should show up in the component list with a green dot to indicate this component is using the new tcl format
  • If you wish to use older versions of your component, you can right click on your component in the SOPC Builder list to select older versions of your component

If your updated component does not appear in the SOPC Builder component list, please refer to Quartus® II Help for information on how to manage and locate your new tcl-based custom components. Altera recommends placing all project-specific SOPC Builder intellectual property (IP) components in the <quartus_project_directory>/ip directory for all new projects.

Upgrade Your Component from the SOPC Builder Component List

  • From SOPC Builder, right click on the component to upgrade, which should have a grey dot next to the component to indicate this is using an older component description file
    • This will open the component directly in the component editor
  • Review the component settings in each tab to make sure the settings have ported correctly
  • In the Component Wizard tab, the component version number has been updated with a higher version number (from x.y to x.y.1)
  • Save your new component description file by clicking Finish
    • A new <component_name>_hw.tcl file is created for your component in the component directory
  • In SOPC Builder, refresh the component list by going to the Refresh Component List in the File menu to update your list of components. The updated component file should show up in the component list with a green dot to indicate this component is using the new tcl format. If you wish to use older versions of your component, you can right click on your component in the SOPC Builder list to select older versions of your component

For information on how to manage and locate your new tcl-based custom components, please refer to Quartus® II Help topic: About SOPC Builder—SOPC Builder Library Components.

Components Not Created by the Component Editor

If you have components not created by the component editor, the component automatic upgrade path will do its best to port the components description information over to the tcl format. However, some non-standard component description information may not be able to be ported to the new tcl format.

After porting the component description file over to the new tcl format, be sure to save your new component tcl file by clicking Finish. This will save the best effort <component_name>_hw.tcl file with your component design files.

You may have to manually modify the tcl file to add some additional component information to make the component tcl file work in the new SOPC Builder tools.

You can read more information on the component tcl file in the Building a Component Interface with Tcl Scripting Commands (PDF) chapter of the Quartus II Development Software Handbook.

For additional help with migrating non-standard component description files, please contact Altera® Support at mysupport.altera.com.

  Please Give Us Feedback