Linux_FUT is a C application for the GNU/Linux operating system based on Trenz Electronic API commands and libusb C API to program USB FX2 microcontroller firmware and FPGA bitstreams.
Info | ||
---|---|---|
| ||
libusb and libusbx release will be officially merged from v1.0.19. These two project/libraries are already actually ("unofficially") merged; see the first table of libusb.org. |
Linux_FUT can be downloaded from here our GiiHub repository.
Note | ||
---|---|---|
| ||
Device Ids of the usb (lsusb): a C construct (#define) is used to choose between Generation 2 (DEWESoft device) and Generation 3 (Trenz Elecronic device). The user should compile and use the Linux_FUT.c file with the correct #define uncommented or the SW tool will not work. |
Code Block | |||
---|---|---|---|
| |||
| |||
// TE USB FX2: generation 2.0 // #define VENDOR_ID 0x0547 // #define PRODUCT_ID 0x1002 // TE USB FX2: generation 3.0 #define VENDOR_ID 0x0BD0 #define PRODUCT_ID 0x0300 |
Linux_FUT can be used (with Generation 2 and/or Generation 3 firmware) for:
Info | ||
---|---|---|
| ||
The two necessary files needed for firmware update and FPGA configuration are usb.bin and fpga.bin. In the past they are normaly , these two files were normally packed together in a file with the extension .fwu . This file is was a zip-file. To unzip it use unzip "file.fwu" . The usb.bin was delivered by the company Trenz Electronic. The fpgaFPGA.bin is was generated with the Xilinx ISE by the user. |
Note |
---|
Linux_FUT cannot be used for recovery boot (Windows only) or modified boot recovery (in both case the USB FX2 microcontroller is running with Cypress VID/PID) in case writing wrong (or corrupted) firmware to EEPROM will hinder/prevent USB conncection with TE USB FX2 modulefirmware recovery. Firmware recovery is necessary when USB connection (with host computer) is nonresponsive. |
Info | ||
---|---|---|
| ||
USB FX2 microcontroller stall term is used to describe the situation where your TE USB FX2 module's FPGA works normally (you are still able to connect to FPGA using JTAG connection) but you are unable to connect to it via USB connection despite having the correct USB drivers installed. |
Writing wrong (or corrupted) firmware to EEPROM will (normally) bring the USB FX2 microcontroller to a standstill. To bring it back out of a standstill, the firmware recovery procedure differs upon the host operating system:stall when the EEPROM firmware is running in FX2 microcontroller's RAM.
FX2 microcontroller's stall will hinder/prevent host computer USB connection (USB connection unresponsive) with TE USB FX2 module.
To bring FX2 microcontroller's back out of this stall and re-establish the host computer USB connection with TE USB FX2 module two firmware recovery procedure are possible:
Under Windows, the user should instead use CyControl, CyConsole or OpenFutNet for a implicit two step recovery boot. After this procedure, the user could use again Linux_FUT again.
Under Linux, the user should instead use fx2loader (see also here) or fxload ( see also here) for a modified an explicit two step recovery boot. After this procedure, the user could use again Linux_FUT again.
Tip |
---|
If the user is unsure about the suitability of a new firmware (wherever it is the source), itIt's a good idea to load it into RAM first to make sure it is not totally broken(and test) custom firmware into FX2 microcontroller's RAM before writing the new firmware into EEPROM; in this way the user/developer could safely test the new firmware. |