Visible to Intel only — GUID: bqj1512449126945
Ixiasoft
1.1. Acronyms and Definitions
1.2. Recommended System Requirements
1.3. Installation Folders
1.4. Boot Flow Overview
1.5. Getting Started
1.6. Enabling the UEFI DXE Phase and the UEFI Shell
1.7. Using the Network Feature Under the UEFI Shell
1.8. Creating your First UEFI Application
1.9. Using Arm* DS-5* Intel® SoC FPGA Edition (For Windows* Only)
1.10. Pit Stop Utility Guide
1.11. Porting HWLIBs to UEFI Guidelines
1.12. Tera Term Installation
1.13. Minicom Installation
1.14. Win32DiskImager Tool Installation
1.15. TFTPd64 By Ph.Jounin Installation
1.16. Revision History of Intel® Arria® 10 SoC UEFI Boot Loader User Guide
1.5.1. Compiling the Hardware Design
1.5.2. Generating the Boot Loader and Device Tree for UEFI Boot Loader
1.5.3. Building the UEFI Boot Loader
1.5.4. Creating an SD Card Image
1.5.5. Creating a QSPI Image
1.5.6. Booting the Board with SD/MMC
1.5.7. Booting the Board with QSPI
1.5.8. Early I/O Release
1.5.9. Booting Linux* Using the UEFI Boot Loader
1.5.10. Debugging an Example Project
1.5.11. UEFI Boot Loader Customization
1.5.12. Enabling Checksum for the FPGA Image
1.5.13. NAND Bad Block Management
Visible to Intel only — GUID: bqj1512449126945
Ixiasoft
1.11.1.3. Type and Macro Names
- Use all capital letters for both #define and typedef declarations. This clearly differentiates static declarations from dynamic data types.
UINT32 UefiVariable
- Each word of a concept shall be separated by an underscore character. The underscore effectively separates the words, making the names more readable.
typedef UINT32 THIS_IS_AN_EXAMPLE_OF_WHAT_TO_DO_FOR_UEFI typedef struct MyStruct { int one; int two; int three; } MY_STRUCT;
- The use of the _t suffix, designating a type, is not allowed.
- The names of guard macros shall end with an underscore character.
#ifndef FILE_NAME_H_ #define FILE_NAME_H_