SBL provides a set of helper libraries like file system support, serial port debug message support, etc. It requires platform specific libraries.Ĭan leverage code interfaces and libraries provided by the bootloader. Implementation depends on SBL source code to build. Payload Types Ī payload can be Tightly Coupled or Loosely Coupled with Slim Bootloader depending on if the payload has code/data dependency or data-only dependency on the bootloader. SBL supports launching customized payloads that provides purpose-driven functionality. It provides secure boot, SMM, and UEFI runtime services. UEFI Payload (External)Ī EDK II based payload implementation to boot Windows. Firmware Update Payload (Built-in)Ī special purpose payload to update full boot flash in a secure and fault-tolerant flow. See Enable Pre-OS Payload Support for more details. When built as an FV formatted payload OS Loader permits the inclusion and launching of a pre-OS payload binary that will hand-off control to an OS after the pre-OS payload finishes execution. It also supports launching OSes compliant with the MultiBoot specification. Payloads Os Loader (Built-in)Ī versatile linux loader implementation that boots Linux, ELF, UEFI-PI FV, or PE executables. It is a modular design to extend bootloader to perform a purpose-driven functionality that is generally independent of platform hardware. SBL payload stage is to boot a target OS.
0 kommentar(er)
