Page History
...
(5b) If libusb or libusbx are used (with WinUSB driver and/or Zadig), the software tools Cypress USB Console, Cypress USB Control Center , Python Open_FUT (Gen2), Python Open_FUT (Gen 3) and C# OpenFutNet could not be directly used. The code of these tools should be rewritten using libusb or libusbx instead of Cypress libraries (CyAPI.lib and CyUSB.dll) and the derived Trenz Electronic libraries (TE_USB_FX2_CyAPI.dll and TE_USB_FX2_CyUSB.dll). See as a starting point for a new software tool using libusb or libusbx under Windows OS.
| Info |
|---|
These libraries are not yet officially supported under Windows, but they are already used with TE USB FX2 modules under Linux . Zadig is not yet officially supported under Windows. |
(6) To default, the FX2 hardware (i.e with EEPROM isolated =>hardware's first stage loader) enumerates the USB FX2 microcontroller chip as VID=0x04B4 (Cypress) and PID=0x8613 (FX2), and provides support for loading firmware into RAM.
...
(7) See section ".
| Note |
|---|
| EEPROM connection shall always be enabled during EEPROM programming. |
| Info |
|---|
Using Cypress firmware update tools with generation 2 modules does require a recovery boot, in order to force enumeration as Cypress USB Generic Driver. On the other side, using Cypress firmware update tools with generation 3 modules may not require a recovery boot (if a Generation 3 reference firmware is running on USB FX2 microcontroller), but only an update boot. This is possible because the original Cypress USB Generic 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 USB Generic Driver. |
...
Overview
Content Tools