AMD design tools
can generate configuration data files in several formats, as described in the following
table. The bitstream generator write_bitstream converts the
post-implementation file into a configuration file or a bitstream. The
write_cfgmem command converts one or more bitstream files into an MCS or
other type of file. The MCS and other write_cfgmem files are known as PROM
files, but the write_cfgmem files can be generated in a number of different
file formats and do not need to be used with a PROM. They can be stored anywhere and
delivered by any means.
| File Extension | Bit Swapping 1 | AMD Tool 2 | Description |
|---|---|---|---|
| BIT | Not bit swapped |
write_bitstream (generated by default) |
Binary configuration data file containing header information that does not need to be downloaded to the FPGA. Used to program devices from the AMD Vivado™ device programmer tool with a programming cable. Proprietary format for Vivado design tool use only. |
| RBT | Not bit swapped | write_bitstream -raw_bitfile | ASCII equivalent of the BIT file containing a
text header and ASCII 1 s and 0 s. Eight bits per
configuration bit. Proprietary format for Vivado design tool use
only. |
| BIN | Not bit swapped | write_bitstream -bin_file | Binary configuration data file with no header information. Can be used for custom configuration solutions (for example, microprocessors), or in some cases to program third-party memories. |
| Bit swapped | write_cfgmem -format BIN | ||
| MCS | Bit swapped 3 |
write_cfgmem -format MCS or Vivado device programmer |
ASCII file format containing address and checksum information in addition to configuration data. Used mainly for device programmers and the Vivado device programmer tool. |
| HEX | Determined by user |
write_cfgmem -format HEX or Vivado device programmer |
ASCII file format containing only configuration data. Used mainly in custom configuration solutions. |
|
|||