https://bugzilla.tianocore.org/show_bug.cgi?id=137https://bugzilla.tianocore.org/show_bug.cgi?id=139
There are four supported methods to generate a boot mode of
BOOT_IN_RECOVERY_MODE on the Galileo platforms:
* Detect a corrupt FV
* Detect a forced recovery from the ForceRecovery UEFI application
that sets a bit in a sticky R/W register
* The RESET button for the Arduino shield is held while the system
is powered up
* The RESET button for the Arduino shield is held while the system
is rebooted using the REBOOT button.
The logic in the PlatformInit module is cleaned up and updated to
support all three of the recovery detection methods. The clean
ups include:
* Remove extra debug messages
* Remove user input from serial port
In addition, once one of the recovery methods is detected and a
boot mode of BOOT_IN_RECOVERY_MODE is set, the Galileo platforms
would get an error attempting to use the USB host controller to
detect and read a recovery image from a USB drive. The issue is
the IMR protection registers are programmed to prevent DMA to
memory owned by the PEI Core. The IMR register programming is
updated to allow DMA to memory that is allocated by the recovery
modules using the PEI AllocatePages() service.
Cc: Kelly Steele <kelly.steele@intel.com>
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Michael Kinney <michael.d.kinney@intel.com>
Reviewed-by: Kelly Steele <kelly.steele@intel.com>
69a0854b8f