Site Search

What data should be used to write data to the external SPI Flash of the FPGA? And how should I create it?

CrossLink Series Diamond ECP Series MachXO Series Radiant

Category: Configuration/Programming
tool:-
device:-

When programming from the CPU to the SPI Flash memory external to the FPGA, use the bit file *.bit.
In Diamond, under the "Export Files" process in the Process window, check the subprocess "Bitstream File" and run it. Radiant automatically generates *.bit when you run the same process.
The generated *.bit file is output under each implementation name folder in the project folder. The implementation name is "impl1" for Diamond and "impl_1" for Radiant unless the user specifies it when generating the project, so the default name is "project name/impl1" or "project name/impl_1".
Some devices support "Dual Boot" which holds two configuration data in SPI Flash, or more "Multi-boot" function. Use *.mcs (usually Intex Hex format) files in this case. Check and run the subprocess "PROM File" under "Export Files". The destination folder is the same as *.bit. You can also use this single *.mcs for SPI Flash programming.
Also, a point tool called "Deployment Tool" is used to consolidate multiple *.bits to generate a dual/multiboot compatible *.mcs.

Experienced FAE
Free consultation is available.

From specific product specifications to parts selection, the Company FAE will answer your technical concerns free of charge. Please feel free to contact us.