241 lines
14 KiB
HTML
241 lines
14 KiB
HTML
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
|
|
"http://www.w3.org/TR/html4/loose.dtd">
|
|
<html>
|
|
<head>
|
|
<meta http-equiv="content-type" content="text/html; charset=iso-8859-1">
|
|
<title>GPIF</title>
|
|
<meta name="generator" content="BBEdit 6.0">
|
|
</head>
|
|
<body bgcolor="white">
|
|
|
|
|
|
<table border="0" cellpadding="0" cellspacing="0" width="90%" align="center">
|
|
<tr valign="top">
|
|
<td colspan="1" align="left" height="13">
|
|
<p align="center"><font face="verdana, arial, helvetica, sans-serif" size="2" color="black"><b><a name="Tools"></a>Tools
|
|
Menu</b></font><font face="verdana, arial, helvetica, sans-serif" size="1" color="black"><b><br> </b></font>
|
|
</td>
|
|
</tr>
|
|
|
|
<tr valign="top">
|
|
<td colspan="1" align="left">
|
|
|
|
<p>
|
|
<font face="verdana, arial, helvetica, sans-serif" size="1" color="black">Several
|
|
essential, but unrelated, functions are presented under the Tools
|
|
menu. These operations allow, among other things, the exporting
|
|
of of defined waveforms to "C" programming language data
|
|
structures. Also, waveforms defined using Cypress' older GPIF
|
|
tool can be imported into </font><font face="Verdana,Arial" size="1" color="black"><i>GPIF
|
|
Designer</i></font><font face="verdana, arial, helvetica, sans-serif" size="1" color="black">
|
|
from the </font><font face="Verdana,Arial" size="1" color="black"><i>Tools</i></font><font face="verdana, arial, helvetica, sans-serif" size="1" color="black">
|
|
menu.<br>
|
|
<br>
|
|
</font>
|
|
</td>
|
|
</tr>
|
|
|
|
<tr valign="top">
|
|
<td colspan="1" align="left">
|
|
<ul>
|
|
<font face="verdana, arial, helvetica, sans-serif" size="1" color="black"><b><a name="SelectBank"></a>Select
|
|
Waveform Bank</b></font>
|
|
</ul>
|
|
|
|
</td>
|
|
</tr>
|
|
|
|
<tr valign="top">
|
|
<td colspan="1" align="left">
|
|
|
|
<ul>
|
|
<p><font face="verdana, arial, helvetica, sans-serif" size="1" color="black">GPIF
|
|
Designer is able to manage up to 8 sets (i.e. banks) of waveform
|
|
descriptors. Each bank consists of 4 waveform descriptors,
|
|
which are displayed on the 4 waveform editor tab pages. At
|
|
any one time, only one bank of waveform descriptors is displayed.
|
|
However, the displayed bank of descriptors can be switched
|
|
via the </font><i><font face="Verdana,Arial" size="1" color="black">Tools|Select
|
|
Waveform Bank</font></i><font face="verdana, arial, helvetica, sans-serif" size="1" color="black">
|
|
menu item.<br></font></p>
|
|
|
|
<p align="center"><font color="black"><img src="images/Bank6.gif" width="432" height="327" border="0"></font></p>
|
|
<p><font face="verdana, arial, helvetica, sans-serif" size="1" color="black">The
|
|
bank number of the currently active waveform bank is displayed
|
|
at the bottom of each waveform editor tab page, as shown above.<br><br>By
|
|
default, only a single waveform bank is enabled. To </font><a href="FileMenu.htm#EnableBanks"><font face="verdana, arial, helvetica, sans-serif" size="1" color="black">enable
|
|
additional banks</font></a><font face="verdana, arial, helvetica, sans-serif" size="1" color="black">,
|
|
use the </font><font face="Verdana,Arial" size="1" color="black"><i>File|Properties</i></font><font face="verdana, arial, helvetica, sans-serif" size="1" color="black">
|
|
menu.<br> </font></p>
|
|
</ul>
|
|
|
|
</td>
|
|
</tr>
|
|
|
|
<tr valign="top">
|
|
<td colspan="1" align="left">
|
|
<ul>
|
|
<font face="verdana, arial, helvetica, sans-serif" size="1" color="black"><b><a name="MapWFSELECT"></a>Map
|
|
Waveforms to WFSELECT</b></font>
|
|
</ul>
|
|
|
|
</td>
|
|
</tr>
|
|
|
|
<tr valign="top">
|
|
<td colspan="1" align="left">
|
|
|
|
<ul>
|
|
<p>
|
|
<font face="verdana, arial, helvetica, sans-serif" size="1" color="black">Each
|
|
of the 4 waveforms can be configured to perform any arbitrary
|
|
function (single/fifo read or write). That is, there is
|
|
no constraint on what function must be implemented on any given
|
|
waveform tab page. For instance, after performing a </font><font face="Verdana,Arial" size="1" color="black"><i>File|New</i></font><font face="verdana, arial, helvetica, sans-serif" size="1" color="black">
|
|
operation, the 4 waveform tabs are labelled, successively
|
|
as </font><font face="Verdana,Arial" size="1" color="black"><i>Single
|
|
Read, Single Write, Fifo Read,</i></font><font face="verdana, arial, helvetica, sans-serif" size="1" color="black">
|
|
and </font><font face="Verdana,Arial" size="1" color="black"><i>Fifo
|
|
Write,</i> as shown below<i>.</i></font><font face="verdana, arial, helvetica, sans-serif" size="1" color="black"> (After
|
|
a </font><font face="Verdana,Arial" size="1" color="black"><i>File|New</i></font><font face="verdana, arial, helvetica, sans-serif" size="1" color="black">
|
|
operation, there are no waveforms defined. So, the labelling
|
|
of the tabs is completely arbitrary.)<br></font>
|
|
<p align="center"><font color="black"><img src="images/NewFile.gif" width="432" height="327" border="0"></font></p>
|
|
<p><font face="verdana, arial, helvetica, sans-serif" size="1" color="black"><br><br>In
|
|
the Fifo design example, shown below, the first waveform tab
|
|
has been used to define a FIFORd operation. The second
|
|
waveform has been used to define a FIFOWr operation. The
|
|
3rd and 4th waveforms are unused.<br></font></p>
|
|
<p align="center"><font color="black"><img src="images/FIFO.gif" width="432" height="327" border="0"></font></p>
|
|
<p><font face="verdana, arial, helvetica, sans-serif" size="1" color="black"><br><br>Because
|
|
there is no requirement that waveform tab labels reflect the
|
|
actual function of the waveform defined on that page, and because
|
|
the designer is allowed the freedom of placing any functional
|
|
waveform on any tab page, a mapping is needed to tell the GPIF
|
|
what function is really found on each waveform tab page. <br><br>This
|
|
mapping is defined in the GPIF register, WFSELECT, and is configured
|
|
via the </font><font face="Verdana,Arial" size="1" color="black"><i>Tools|Map
|
|
Waveforms to WFSELECT . . .</i></font><font face="verdana, arial, helvetica, sans-serif" size="1" color="black">
|
|
menu item. The </font><font face="Verdana,Arial" size="1" color="black"><i>Map
|
|
Waveforms to WFSELECT</i></font><font face="verdana, arial, helvetica, sans-serif" size="1" color="black">
|
|
dialog box is shown below, with the configuration of the FIFO
|
|
design example.</font></p>
|
|
<p align="center"><font color="black"><img src="images/WFSELECT.gif" width="432" height="327" border="0"><br></font></p>
|
|
<p align="left"><font color="black" face="Verdana" size="1"><br><br>Note
|
|
that, after a <i>File|New</i> operation, the 4 waveforms have
|
|
been mapped into WFSELECT such that the function named in the
|
|
tab label would be appropriate for that tab sheet. That
|
|
is, after a <i>File|New</i> operation, the designer could implement
|
|
the <i>Single Read</i> function in the first waveform, the
|
|
<i>Single Write</i> function in the second waveform, the <i>FIFO
|
|
Read </i>function in waveform #3 and the <i>FIFO Write</i> function in
|
|
the last waveform. If the designer created these waveform
|
|
functions, corresponding to the default waveform tab labels,
|
|
the WFSELECT mapping would not need to be changed.</font></p>
|
|
<p align="center"><font color="black"><img src="images/DefaultWFSELECT.gif" width="432" height="327" border="0"> </font></p>
|
|
<p><font face="verdana, arial, helvetica, sans-serif" size="1" color="black"><br>
|
|
</font></p>
|
|
|
|
</ul>
|
|
|
|
</td>
|
|
</tr>
|
|
|
|
<tr valign="top">
|
|
<td colspan="1" align="left">
|
|
<ul>
|
|
<font face="verdana, arial, helvetica, sans-serif" size="1" color="black"><b><a name="Export"></a>Export
|
|
to GPIF.c file</b></font>
|
|
</ul>
|
|
|
|
</td>
|
|
</tr>
|
|
|
|
<tr valign="top">
|
|
<td colspan="1" align="left">
|
|
|
|
<ul>
|
|
<p>
|
|
<font face="verdana, arial, helvetica, sans-serif" size="1" color="black">The
|
|
principal objective in defining a set of GPIF waveforms is to
|
|
generate the waveform descriptors, as "C" language
|
|
data structures for inclusion in a firmware project
|
|
for the FX / FX2. Once the block diagram has been specified
|
|
and the waveforms have been correctly defined using the waveform
|
|
editors, GPIF Designer can generate correct "C" language
|
|
data structures to be used in programming the device. <br><br>The
|
|
generation of the data structures is accomplished via the </font><font face="Verdana,Arial" size="1" color="black"><i>Tools|Export
|
|
to GPIF.c file</i></font><font face="verdana, arial, helvetica, sans-serif" size="1" color="black">
|
|
menu item. When this menu item is invoked, the user will
|
|
be prompted to specify a location and file name for the data
|
|
structures. It is important to understand that the </font><font face="Verdana,Arial" size="1" color="black"><i>Export
|
|
to GPIF.c file</i></font><font face="verdana, arial, helvetica, sans-serif" size="1" color="black">
|
|
function completely over-writes the specified file with
|
|
the waveform descriptor data. It does NOT merely append
|
|
or insert the data structures into an existing file. For
|
|
this reason, the user will usually want to specify a new file
|
|
as the target of the Export operation.<br><br>Also note that
|
|
it is not necessary to export the waveform descriptor data structures
|
|
to the same directory as the GPIF Designer project file.<br><br>The
|
|
file generated by the Tools|Export to GPIF.c file function contains
|
|
many comments reflecting the original GPIF Designer project
|
|
file from which the data structures were derived. These
|
|
comments contain strings that reflect waveform tab labels and
|
|
block diagram configurations such as CTL and RDY line labels.
|
|
In order to generate a "*.c" file compatible
|
|
with the older GPIF tool, many of these labels are truncated
|
|
when exported to the "*.c" file. One should
|
|
expect to lose some string information if attempting to import
|
|
a file generated by the Tools|Export to GPIF.c file operation.<br><br>The
|
|
primary vehicle for saving and loading GPIF waveform designs
|
|
is the </font><font face="Verdana,Arial" size="1" color="black"><i>File</i></font><font face="verdana, arial, helvetica, sans-serif" size="1" color="black">
|
|
menu. The </font><font face="Verdana,Arial" size="1" color="black"><i>Tools|Export/Import</i></font><font face="verdana, arial, helvetica, sans-serif" size="1" color="black">
|
|
functions do not retain or recover all the information stored
|
|
in a GPIF Designer (*.gpf) file.<br> </font>
|
|
</ul>
|
|
|
|
</td>
|
|
</tr>
|
|
|
|
<tr valign="top">
|
|
<td colspan="1" align="left">
|
|
<ul>
|
|
<font face="verdana, arial, helvetica, sans-serif" size="1" color="black"><b><a name="Import"></a>Import
|
|
older GPIF.c file</b></font>
|
|
</ul>
|
|
|
|
</td>
|
|
</tr>
|
|
|
|
<tr valign="top">
|
|
<td colspan="1" align="left">
|
|
|
|
<ul>
|
|
<p>
|
|
<font face="verdana, arial, helvetica, sans-serif" size="1" color="black">GPIF
|
|
Designer is the second-generation of Cypress tools for defining
|
|
GPIF waveform descriptors for the FX/FX2. Waveform descriptors
|
|
generated by the previous tool can be read into GPIF Designer
|
|
via the</font><font face="Verdana,Arial" size="1" color="black"><i>
|
|
Tools|Import older EZ-USB FX GPIF.c file</i></font><font face="verdana, arial, helvetica, sans-serif" size="1" color="black">
|
|
and </font><font face="Verdana,Arial" size="1" color="black"><i>Tools|Import
|
|
older FX2 GPIF.c file</i></font><font face="verdana, arial, helvetica, sans-serif" size="1" color="black">
|
|
menu items.<br><br>Because the file formats generated by the
|
|
older tool differ for EZ-USB FX and FX2, separate import menu
|
|
items are used to import the appropriate file types. Be
|
|
sure to invoke the correct operation for the file type that
|
|
is to be imported.<br><br>Note that, in order for the import
|
|
functions to work, the target file must be in a format compatible
|
|
with the old tool. If the file has been manually modified
|
|
so as to render its format incompatible with the older
|
|
GPIF tool, the import functions will fail to import the file.<br> </font>
|
|
</ul>
|
|
|
|
</td>
|
|
</tr>
|
|
|
|
</table>
|
|
</font>
|
|
</body>
|
|
</html>
|