Scroll pdf title | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
...
(8) Version ≥ 2.0
(9) Version≥ 4.0.30319)
The following firmware tools
...
work only if the 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 require 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.
...
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).