原创 Upgrading from .PTF-format to .SOPC-format

Upgrading from .PTF-format to .SOPC-format

Recommendations & Explanation
Version 7.1 is a major new release for SOPC Builder. A key change is the new file format for storing system design data. Previously, SOPC Builder used a proprietary file format (PTF) to store system designs, while SOPC Builder version 7.1 uses an industry standard XML file format for data storage. By convention, these files are given the extension ".sopc".

Motivation for Migrating to XML (.sopc) Format
Previous versions of SOPC Builder used the PTF file as both a source document and as a working database. During SOPC Builder's generation-phase (the operations which take place when you press the "Generate..." button), various programs would both read and modify the system PTF file. This behavior made SOPC Builder project files difficult to integrate with source control, and with scripted build and regression flows, such as those using make.

The Role of the New .sopc File
SOPC Builder can be thought of in two parts: An editor, which creates and modifies source-documents, and a generator, which generates various output-files (RTL, simulator-setup files, etc.). In version 7.1, the SOPC Builder editor (GUI) works only on the .sopc file. The .sopc file is a pure source document, suitable for use with revision-control systems and scripted build and regression flows. The generator takes the .sopc-file as an input, and generates outputs such as software support and HDL.
SOPC Builder 7.1 also improves the separation of the system model (as captured by the .sopc document), and the view of the system. This will allow SOPC Builder to support a scripting interface and a variety of system views.

The Continued Presence of PTF-files
In v7.1, the SOPC Builder generator creates a PTF file when generating the system, even for new designs which were created using the .sopc format. This.ptf file is generated to support SOPC Builder related tools such as the Nios II IDE and scripted build flow. As of release 7.1 of SOPC Builder, use of the PTF-file for any other purpose is deprecated. Altera and partner tools will phase out the use of PTF files over time. Going forward, the preferred method for tools to read or modify system information is through a well-defined API. Contact Altera for information about SOPC Builder SDK-availability.

Compatibility when Migrating from PTF to .sopc Formats
If you have an existing SOPC Builder design, the surest way to guarantee compatibility in 7.1 is to open SOPC Builder "Classic". Here's how:
    1. When you open a PTF file in SOPC Builder, you will see a dialog which provides the option of opening your system in "classic" mode
    2. You may run SOPC Builder from the command-line and provide the "--classic" switch.
    3. You may set the environment-variable $SOPC_BUILDER_CLASSIC = 1
For designs near the end of their development cycle, Altera recommends editing and generation using "classic" mode , to guarantee backwards compatibility.
For new designs, those early in the designs cycle, and those that require the new features of SOPC Builder 7.1, Altera recommends using the new .sopc file format. For new designs using v7.1, this happens with no action on the designers part. For existing PTF based designs, select the "Upgrade" button on the starting dialog to attempt to upgrade the design automatically to SOPC Builder v7.1. If you encounter any problems upgrading an existing PTF-design, please contact Altera. Please provide a complete Quartus project directory, along with your original PTF file, so we can quickly resolve the problem.

    相关链接：Avalon_Microsequencer初步调试成功

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