This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
en:ztex_boards:ztex_fpga_boards:indirect_flash_programming [2014/04/15 19:37] – angelegt 84.181.55.29 | en:ztex_boards:ztex_fpga_boards:indirect_flash_programming [2023/10/30 17:35] (current) – stefan | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== | + | ====== |
- | [[http:// | + | [[http:// |
+ | |||
+ | **The method described here does not work with EZ-USB FX3 based boards because they completely handle the FPGA configuration process per Firmware. ** | ||
The brand of SPI Flash which is used on ZTEX FPGA Boards may vary (mostly Spansion S25FL127S or S25FL216K) but all types support a set of basic commands which make them compatible (and usable with the same EZ-USB Firmware). | The brand of SPI Flash which is used on ZTEX FPGA Boards may vary (mostly Spansion S25FL127S or S25FL216K) but all types support a set of basic commands which make them compatible (and usable with the same EZ-USB Firmware). | ||
Line 10: | Line 12: | ||
</ | </ | ||
Then, a standard device can be selected in Impact, e.g. M25P128 for 128MBit chips or M25P16 for 16MBit chips. | Then, a standard device can be selected in Impact, e.g. M25P128 for 128MBit chips or M25P16 for 16MBit chips. | ||
+ | |||
+ | By default firmware only attempts to configure the FPGA from Flash if the bitstream size value in the settings memory (MAC-EEPROM) is larger than 0. This mechanism saves a lot of time if not bitstream is present, but only works if bitstream is written through the firmware. This behavior can be overwritten by specifying the firmware macro '' | ||
+ | |||
+ | Indirect programming of SPI Flash requires Flash access form FPGA, see [[en: |