View Source

Generation 2 and generation 3 technology stacks share the same firmware but with different VIDs/PIDs.

The following firmware tools

DEWESoft FUT (firmware upgrade tool)
Open_FUT (generation 2, Firmware Upgrade and FPGA Configuration)
Open_FUT (generation 3, Firmware Upgrade and FPGA Configuration using a simplified TE_USB_FX2_CyAPI.dll)
OpenFutNet (generation 3, Firmware Upgrade and FPGA Configuration are using both CyUSB.dll and TE_USB_FX2_CyUSB.dll )

work only reference firmware, or a derived firmware is running in the module. The reference/derived firmware is necessary because the three tools make use of TE API Commands (see the corresponding API reference manual) executed by the USB FX2 microcontroller. These tools are therefore able to update the firmware (EEPROM programming) of the USB FX2 microcontroller and the FPGA configuration file (bitstream, SPI Flash programming).

Note: some TE API Commands requires support from a Xilinx MicroBlaze soft embedded processor (of the TE reference/derived architecture), but this TE API Commands are not needed for EEPROM and SPI Flash programming.

The following firmware tools

Cypress USB Console (Recovery Procedure uses CyAPI.lib)
Cypress USB Control Center (Recovery Procedureuses CyUSB.dll)
OpenFutNet (Recovery Procedure uses CyUSB.dll)

work also if the reference firmware, or a derived firmware is not running in the module. The reference/derived firmware is not necessary because they do not make use of TE API Commands. Conversely, they directly make use of CyAPI.lib and CyUSB.dll, respectively. These two tools are therefore only able to update the firmware of the USB FX2 microcontroller, but not the FPGA configuration file (bitstream).

Tool	Gen 2 Firmware Upgrade: requires DEWESoft device driver and DEWESoft API	Gen 3 Firmware Upgrade: requires TE USB FX2 device driver and TE API	Firmware Recovery: requires USB generic Cypress device driver, to boot with EEPROM disabled and to enable EEPROM after TE USB FX2 module is inserted into USB port	FPGA Configuration	Microsoft .NET Framework	Python 2.7 interpreter
DEWESoft Firmware Upgrade Tool	yes	no	no	yes	no	no
Open_FUT for generation 2	yes	no	no	yes	no	yes
Open_FUT for generation 3	no	yes; it use a simplified TE_USB_FX2_CyAPI.dll	no	yes; it use a simplified TE_USB_FX2_CyAPI.dll	no	yes
CyConsole = Cypress USB Console	no	yes	yes, Recovery Boot	no	no	no
CyControl = Cypress USB Control Center	no	yes	yes, Recovery Boot	no	yes	no
OpenFutNet: 3 procedures are available	no, Recovery Procedure should be used instead	yes, Firmware Upgrade; it use both CyUSB.dll and TE_USB_FX2_CyUSB.dll	yes, Recovery Procedure; it use CyUSB.dll	yes, FPGA Configuration; it use both CyUSB.dll and TE_USB_FX2_CyUSB.dll	yes, (version ≥ 4.0.30319)	no

Generation 2

VID/PID:

0x0547/0x1002

Firmware files:

TE-USB-FX2_current_DW.iic https://github.com/Trenz-Electronic/TE-USB-Suite/tree/master/TE_USB_FX2.firmware/ready_for_download

Firmware update tools:

DEWESoft Firmware Upgrade Tool:It requires DEWESoft device driver and DEWESoft API.It work only if the DEWESoft reference/derived firmware is running in the module.DEWESoft FUT is able to update the firmware of the USB FX2 microcontroller and the FPGA configuration file (fpga.bin bitstream).
Open_FUT for generation 2:It requires DEWESoft device driver, Python and DEWESoft API.It works only if the DEWESoft reference/derived firmware is running in the module.Open_FUT is able to update the firmware of the USB FX2 microcontroller and the FPGA configuration file (bitstream fpga.bin).
CyConsole = Cypress USB Console:It requires Cypress generic USB device driver and CyAPI.lib static library.It works also if the DEWESoft reference/derived firmware is not running in the module.It is used as recovery USB firmware tool (recovery boot)It requires to boot with EEPROM switched off (DEWESoft device is registered as Cypress device), then back on (EEPROM can be written).Some documentation in UM-USB-Firmware.pdf.Some examples here (firmware restore only).
CyControl = Cypress USB Control Center (requires .NET Framework):It requires Cypress generic USB device driver, .Microsoft NET Framework (version ≥ 4.0.30319) and CyUSB.dll dynamic library.It works also if the DEWESoft reference/derived firmware is not running in the module.It is used as recovery USB firmware tool (recovery boot)It requires to boot with EEPROM switched off (DEWESoft device is registered as Cypress device), then back on (EEPROM can be written).Some examples here (firmware restore only).

Documentation

CyConsole = Cypress USB Console: http://www.trenz-electronic.de/download/d0/Trenz_Electronic/d1/TE-USB-Suite/d2/generation_2/d3/documents.html

Generation 3

VID/PID:

0x0BD0/0x0300

Firmware files:

TE-USB-FX2_current_TE.iic https://github.com/Trenz-Electronic/TE-USB-Suite/tree/master/TE_USB_FX2.firmware/ready_for_download

Firmware update tools:

Open_FUT for generation 3:It requires TE USB FX2 device driver, Python and a pure extern C code library version of TE_USB_FX2_CyAPI APIs (codename: simplified TE_USB_FX2_CyAPI APIs).It works only if the Trenz Electronic reference/derived firmware is running in the module.Open_FUT is able to update the firmware of the USB FX2 microcontroller and the FPGA configuration file (bitstream fpga.bin).
CyConsole = Cypress USB Console:It requires Cypress generic USB device driver and CyAPI.lib static library.It works also if the Trenz Electronic reference/derived firmware is not running in the module.Boot with EEPROM switched off is not required.Some documentation in UM-USB-Firmware.pdf.Some examples here (firmware restore) and here (firmware update).
CyControl = Cypress USB Control Center (requires .NET Framework);It requires Cypress generic USB device driver, .Microsoft NET Framework (version ≥ 4.0.30319) and CyUSB.dll dynamic library.It works also if the reference/derived architecture is not running in the module.Boot with EEPROM switched off is not required.Some examples here (firmware restore) and here (firmware update).

Documentation

CyConsole = Cypress USB Console: http://www.trenz-electronic.de/download/d0/Trenz_Electronic/d1/TE-USB-Suite/d2/generation_2/d3/documents.html

Recovery Boot

A recovery boot is a multi-step boot operation:

module is off and connected;
EEPROM switch is set off;
module is powered on;
module enumerates in recovery mode (VID = 0x04B4, PID = 0x8613);the module is served by the Cypress generic USB device driver;the Cypress generic USB device driver allows Cypress firmware update tools (Cypress Console, Cypress Control Center) to work with the Cypress EZ-USB FX2 microcontroller on the module;
EEPROM switch is set back on;Cypress firmware update tools can read and write the EEPROM.

Using Cypress firmware update tools with generation 2 modules does require a recovery boot, in order to force enumeration as Cypress generic USB device driver.
On the other side, using Cypress firmware update tools with generation 3 modules does not require a recovery boot. This is possible because the original Cypress generic USB device driver (in case of a recovery boot) and the Trenz Electronic USB FX2 device driver ( in case of a regular boot) are both Cypress driver. Trenz Electronic USB FX2 driver derives from the original Cypress generic USB device driver.
EEPROM switch shall always be on during EEPROM programming.
The firmware update procedure is similar for both generations. The following table summarizes the main differences.

generation	2: recovery boot	3: recovery boot	3: regular boot
boot mode (EEPROM switch)	recovery (off, then on)	recovery (off, then on)	regular (always on)
VID	04B4	04B4	0BD0
PID	8613	8613	0300
device	Cypress generic USB	Cypress generic USB	TE USB FX2
required driver	recovery driver	recovery driver	regular driver
update applications	Cypress USB Console Cypress USB Control Center

Further information is shown in the following video play lists.