A visual representation of the contents of a Hexadecimal (Intel-Format) Output File (.hexout), Raw Binary File (.rbf), Tabular Text File (.ttf), Hexadecimal (Intel-Format) Output File for EPC16 (.hexout), or Hexadecimal (Intel-Format) Output File for SRAM (.hexout). For a Programmer Object File (.pof), POF for Remote Update, and POF 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 (File menu).

For a POF for an EPC1, EPC1441, or EPC2 configuration device, the configuration memory space represents the chain of SOFs in the order in which they are stored in the configuration device.

For a POF for an EPC4, EPC8, or EPC16 configuration device, the configuration memory space represents the placement of the SRAM Object File (.sof) and Hexadecimal (Intel-Format) File (.hex) within the flash memory of the configuration device. The configuration memory space represents the HEX 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 SOFs within each parallel bit within 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 APEX^™ II, Stratix^™, and Stratix^™ GX devices in Fast Passive Parallel mode (FPP). In FPP mode, the configuration memory space contains the same information as when creating a POF for an EPC4, EPC8, or EPC16 configuration device, except FPP mode allows only a data width of 8 bits within each page.

The following table displays the combinations of Mode and Page settings for each programming file type and configuration device:

Back to Top