A visual representation of the contents of a Hexadecimal (Intel-Format) Output File (.hexout), Hexadecimal (Intel-Format) Output File for EPC16 (.hexout), Hexadecimal (Intel-Format) Output File for SRAM (.hexout), Raw Binary File (.rbf), Raw Programming Data File (.rpd), or Tabular Text File (.ttf). For a Programmer Object File (.pof), Programmer Object File for Remote Update, and Programmer Object File for Local Update, the configuration memory space represents the contents of a specific configuration device. This visual representation appears in the Input files to convert list in the Convert Programming Files dialog box.
For a Programmer Object File for an EPC1, EPC1441, or EPC2 configuration device, the configuration memory space represents the chain of SRAM Object Files (.sof) in the order in which they are stored in the configuration device.
For a Programmer Object File for an EPC4, EPC8, or EPC16 configuration device, the configuration memory space represents the placement of the SRAM Object Files and Hexadecimal (Intel-Format) Files (.hex) in the flash memory of the configuration device. The configuration memory space represents the Hexadecimal (Intel-Format) Files stored in the Bottom Boot Data and Main Boot Block sections of the flash memory. The configuration memory space also represents the contents of up to eight pages of data, each with the capacity to store a unique configuration bitstream. It also can store the chain of SRAM Object Files in each parallel bit in each page of data, if any, in the order in which they are stored in the configuration device. An EPC4, EPC8, or EPC16 configuration device can also be used to program supported devices in Fast Passive Parallel mode ( FPP). In Fast Passive Parallel mode, the configuration memory space contains the same information as when creating a Programmer Object File for an EPC4, EPC8, or EPC16 configuration device, except Fast Passive Parallel mode allows only a data width of 8 bits in each page.
For JTAG Indirect Configuration Files (.jic), the configuration memory space represents the placement of the SRAM Object Files and Hexadecimal (Intel-Format) Files in the flash memory of the configuration device, as well as information about the device used as a bridge between the Programmer or external controller and the configuration device when programming the configuration device.
The following table displays the combinations of Mode and Page settings for each programming file type and configuration device:
|
Programming File Type (and Configuration Device) |
Mode |
Pages |
|---|---|---|
|
Programmer Object File (EPC4, EPC8, EPC16) |
1-, 2-, 4-, 8-bit Passive Serial |
1 - 8 |
|
Programmer Object File (EPC4, EPC8, EPC16) |
1-, 2-, 4-, 8-bit Passive Serial Fast Passive Parallel |
1 - 8 |
|
Programmer Object File (EPC1, EPC1441, or EPC2) |
1-bit Passive Serial |
1 |
|
Programmer Object File (EPCS1 or EPCS4) |
Active Serial Configuration |
1 |
|
Programmer Object File for Remote Update (EPC4, EPC8, or EPC16) |
1-bit Passive Serial |
1 - 8 |
|
Programmer Object File for Local Update (EPC4, EPC8, or EPC16) |
1-bit Passive Serial |
1 |
|
Hexadecimal (Intel-Format) Output File for EPC16 (EPC16) |
1-bit Passive Serial |
1 |
|
Hexadecimal (Intel-Format) Output File for SRAM, Raw Binary File, Tabular Text File |
1-bit Passive Serial Passive Parallel Asynchronous Passive Parallel Synchronous |
1 |
|
Hexadecimal (Intel-Format) Output File for SRAM, Raw Binary File, Tabular Text File |
1-bit Passive Serial Passive Parallel Asynchronous Passive Parallel Synchronous Fast Passive Parallel |
1 |
|
JTAG Indirect Configuration Files |
Active Serial Configuration |
1 |