You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 2dea400
Browse filesBrowse the repository at this point in the historyBrowse files
Copy file name to clipboardExpand all lines: docs/Targets.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9111,6 +9111,7 @@ Notable options in [config/examples/nai_68int6.config](../config/examples/nai_68
9111
9111
|`X86_UART_NUMBER=2`| LPSS UART2 for all three FSP phases (Kontron uses 0) |
9112
9112
|`ACPI=1`| Required. Generates ACPI tables (RSDP/XSDT/FADT/MADT/MCFG/TPM2/HPET/DMAR and a minimal DSDT with the TPM device); the board's PCI interrupt routing is only in the DSDT `_PRT`, since the MP table is the Kontron one. The DSDT also declares the board devices on LPSS I2C0 (EEPROMs, RTC/watchdog) and GSPI0 (the PRC, for NAI's `naigspi` driver) |
9113
9113
| `FSP_NVS_CACHE=1`, `FSP_NVS_BASE`, `FSP_NVS_SIZE` | Keeps FSP-M's memory training data (its non-volatile storage HOB) in a 128 KB area of the BIOS region below the wolfBoot window, so later boots skip full memory training. Stage 1 passes a valid copy back through `NvsBufferPtr`; stage 2 rewrites it, before FSP-S and before the BIOS region is locked, only when it changes. The record is keyed on a CRC of the FSP-M image and its UPDs, so a change to either falls back to full training. Stage 1 sets a CMOS flag before FspMemInit runs with a saved record, an FSP-requested reset clears it, and stage 2 clears it once FspSiliconInit succeeds. If FspMemInit fails with the record, or a boot finds the flag still set because the previous boot crashed or hung with the record, boots train from scratch until one gets through FspSiliconInit, and stage 2 replaces the record. The flag is kept in CMOS, so it survives a reset but needs the RTC battery to survive loss of power. `assemble_image.sh -n` blanks the area, so an image built from a board's flash dump does not carry that board's training data |
9114
+
|`FSP_NVS_TPM=1`| Authenticates the saved training data, which is otherwise the only unauthenticated input FSP-M consumes. Stage 2 keeps a SHA-256 of the record in a TPM NV index that only the platform hierarchy can write, and stage 1 reads it, before memory is up, and compares it with the record in flash before handing the record to FspMemInit; without a match it trains from scratch. Needs `ANTI_ROLLBACK=1`, which disables the platform hierarchy before handoff so the OS cannot rewrite the hash. The first boot after enabling it trains once. Without this option, prefer `FSP_NVS_CACHE=0` on a Boot Guard image |
9114
9115
|`FSP_HYPERTHREADING=1`| Hyper-Threading on (off by default). The MADT and the MP table list the enabled logical processors from the CPUID topology, so either setting works |
9115
9116
|`MP_CPU_NUM_ENTRY=8`| MP table processor entries, one per logical processor (default 4) |
9116
9117
|`WOLFBOOT_CMDLINE_MAX`| Buffer for a signed `HDR_CMDLINE`, including the terminating NUL (default 256); a longer command line is ignored and the built-in one is used |
0 commit comments