Visible to Intel only — GUID: xcn1502039440557
Ixiasoft
1. Introduction to the Intel® Stratix® 10 SoC Device Design Guidelines
2. Board Design Guidelines for Stratix 10 SoC FPGAs
3. Interfacing to the FPGA for Stratix 10 SoC FPGAs
4. System Considerations for Stratix 10 SoC FPGAs
5. Embedded Software Design Guidelines for Intel® Stratix® 10 SoC FPGAs
6. Recommended Resources for Stratix 10 SoC FPGAs
2.1. Pin Connection Considerations for Board Design
2.2. HPS Clocking and Reset Design Considerations
2.3. Design Considerations for Connecting Device I/O to HPS Peripherals and Memory
2.4. Design Guidelines for HPS Interfaces
2.5. HPS EMIF Design Considerations
2.6. HPS Memory Debug
2.7. Boundary Scan for HPS
2.8. Embedded Software Debugging and Trace
2.9. Board Design Guidelines for Intel® Stratix® 10 SoC FPGAs Revision History
3.1. Overview of HPS Memory-Mapped Interfaces
3.2. Recommended System Topologies
3.3. Recommended Starting Point for HPS-to-FPGA Interface Designs
3.4. Timing Closure for FPGA Accelerators
3.5. Information on How to Configure and Use the Bridges
3.6. Interfacing to the FPGA for Intel® Stratix® 10 SoC FPGAs Revision History
5.1. Overview
5.2. Assembling the Components of Your Software Development Platform
5.3. Golden Hardware Reference Design (GHRD)
5.4. Selecting an Operating System for Your Application
5.5. Assembling Your Software Development Platform for Linux*
5.6. Assembling your Software Development Platform for a Bare-Metal Application
5.7. Assembling your Software Development Platform for Partner OS or RTOS
5.8. Choosing the Bootloader Software
5.9. Selecting Software Tools for Development, Debug and Trace
5.10. Boot And Configuration Considerations
5.11. System Reset Considerations
5.12. Flash Considerations
5.13. Embedded Software Debugging and Trace
5.14. Embedded Software Design Guidelines for Intel® Stratix® 10 SoC FPGAs Revision History
Visible to Intel only — GUID: xcn1502039440557
Ixiasoft
3.2.3.2. Example 2: FPGA Writing Data into HPS SDRAM Directly
In this example the HPS MPU requires access to data that originates from within the FPGA. For the MPU to be able to access the data coherently after it is written, software may need to flush or invalidate cache lines before the transfer starts, to ensure that the SDRAM contains the latest data after it is written. Failing to perform cache operations can cause one or more cache lines to eventually become evicted overwriting the data that was written by the FPGA master.
Figure 14. FPGA Writing Data to HPS FPGA-to-SDRAM PortsThis figure depicts an example of using two of the three F2S ports configured for 128 bits in width.
Note: Like in Example 1: FPGA Reading Data from HPS SDRAM Directly, where the FPGA reads data from the FPGA-to-SDRAM ports, you can maximize write throughput into the HPS SDRAM by using multiple 128-bit FPGA-to-SDRAM ports with at least one master in the FPGA connected to each port.