...
In any case, even an EEPROM written with a malfuctioning/broken firmware could be easily corrected with an implicit two step recovery toot (TE USB FX2 Firmware Recovery) or a explicit two step recovery boot.
Firmware modification dependencies
| Scroll Title |
|---|
| title | Firmware modification dependencies |
|---|
|
| Host computer's SW will be | To do so, the developer should
create a custom FX2 microcontroller's firmware | To do so, the developer should
modify the FPGA's MicroBlaze software |
|---|
able to use custom USB FX2 API Commands
and reference USB FX2 API Commands | compatible with the reference firmware; | no change of FPGA's MicroBlaze software
should be necessary | | able to use SPI Flash Commands, | that keep a compatible FLASH_WRITE_COMMAND
command in FW; | no change of FPGA's MicroBlaze software
should be necessary | | able to use custom MB Commands | no change of FX2 microcontroller's firmware
should be necessary; | modify MicroBlaze API Commands in the i2c_slave_int_handler() function in interrupt.c
running on FPGA's MicroBlaze
(using the demo project as starting point); | use the interrupts associated with MB Commands
in a different way (aka avoid polling for example) | create a custom FX2 microcontroller's firmware that modify GET_INTERRUPT command,
SET_INTERRUPT command, | modify the i2c_slave_int_handler() function
in interrupt.c running on FPGA's MicroBlaze
and (maybe) modify the
VHDL XPS_I2C_SLAVE custom IP block | use Slave Parallel (SelectMAP) Mode and/or
Slave Serial Mode | that load the configuration data from a source (SPI Flash,
USB connection or B2B connection) and write the retrieved
configuration data in the FPGA. | no change of FPGA's MicroBlaze software
should be necessary,
but some HW modifications
(desoldering/resoldering) are necessary for
TE0630 and TE0300 module |
|
...