Visible to Intel only — GUID: sss1411547027320
Ixiasoft
1.1. Features
1.2. Device Support
1.3. Functional Description
1.4. Using the PFL IP Core
1.5. PFL IP Core In Embedded Systems
1.6. Third-party Programmer Support
1.7. Parameters
1.8. Signals
1.9. Specifications
1.10. Parallel Flash Loader Intel® FPGA IP User Guide Archives
1.11. Document Revision History for the Parallel Flash Loader Intel® FPGA IP User Guide
1.4.1. Converting .sof Files to a .pof
1.4.2. Constraining PFL Timing
1.4.3. Simulating PFL Design
1.4.4. Programming Intel® CPLDs and Flash Memory Devices
1.4.5. Defining New CFI Flash Device
1.4.6. Programming Multiple Flash Memory Devices
1.4.7. Creating Jam Files for Intel® CPLDs and Flash Memory Device Programming
Visible to Intel only — GUID: sss1411547027320
Ixiasoft
1.3.6.2. Implementing Remote System Upgrade with the PFL IP Core
You can achieve the remote system upgrade capabilities with the PFL IP core by controlling the fpga_pgm[2..0] and the pfl_nreconfigure ports.
To control the fpga_pgm[2..0] and the pfl_nreconfigure ports, user-defined logic must perform the following capabilities:
- After FPGA power-up, user logic sets the fpga_pgm[2..0] ports to specify which page of configuration image is to be loaded from the flash.
- After the remote host completes the new image update to the flash, user logic triggers a reconfiguration by pulling the pfl_nreconfigure pin low and setting the fpga_pgm[2..0] to the page in which the new image is located. The pfl_nreconfigure signal pulsed low for greater than one pfl_clk cycle.
- If you have enabled the user watchdog timer, user logic can monitor the pfl_watchdog_error port to detect any occurrence of watchdog time-out error. If the pfl_watchdog_error pin is asserted high, this indicates watchdog time-out error. You can use the user logic to set the fpga_pgm[2..0] and pull the pfl_nreconfigure port low to initiate FPGA reconfiguration. The recovery page to be loaded from the flash memory device after watchdog timer error depends on the fpga_pgm[2..0] setting.
Figure 17. Implementation of Remote System Upgrade with the PFL IP Core