Logo
  • Get Started
  • Boot Infrastructure
    • PBL
    • XBL
    • UEFI
      • Development
        • CustomSplashLogo
          • Supported Image formats
          • Logo File Naming
          • Adding the logo file to the firmware volume (FV)
            • How to add logo bitmap
            • Mapping the display to the logo image file
        • HowToAddPanel
        • ImageFv
        • MMU
        • MultiThreading
        • UefiLogBufferSizeConfigReadme
        • UEFISchedulerUnsafeStackSupport
      • Drivers
      • Debug
      • Applications
      • Tools
    • RamDump
    • Device Programmer
  • Open Source
Pakala
  • Boot Infrastructure
  • UEFI
  • Development
  • CustomSplashLogo
  • View page source

CustomSplashLogo¶

Supported Image formats¶

  • 8-bit BMP

  • 24-bit BMP

  • 32-bit BMP

  • 8-bit indexed BMP

Compressed bitmaps are not supported.

Note

Since the firmware volume is already compressed, any BMPs being stored inside will also be compressed automatically.

Logo File Naming¶

Logos should be named as logo1.bmp, logo2.bmp, logo3.bmp …

The default configuration of the driver is to use logo1.bmp as the filename for the default logo, but this can be overwritten using the steps below.

Adding the logo file to the firmware volume (FV)¶

Add logo files into Fv and select which logo should be used for display.

How to add logo bitmap¶

  1. Adding logo bitmap to the FV compilation.

    Put logo bitmap such as logo1.bmp into QcomPkgLogoCommon folder.

  2. Injecting the logo bitmap in to the firmware volume (FV).

    User could choose to save logo bitmap in MainFv or ImageFv.

    Note

    The MainFv may have limited space so larger logos should move to the ImageFv.

    1. How to enable MainFv

      Add the entry for the logo1.bmp in QcomPkgSocPkg[TARGET]CommonCore.fdf:

      FILE FREEFORM = 8f2a919c-35f3-4cb5-8541-689f58c5f018 {
          SECTION UI = "logo1.bmp"
          SECTION RAW = QcomPkg/Logo/Common/logo1.bmp
      }
      
    2. How to enable ImageFv

      1. Set “EnableDisplayImageFv = 0x1” in QcomPkgSocPkg[TARGET]Commonuefiplat.cfg.

      2. Add the entry for the logo1.bmp in QcomPkgSocPkg[TARGET][LAA|LAB|WP]ImageFv.fdf.inc:

        FILE FREEFORM = 8f2a919c-35f3-4cb5-8541-689f58c5f018 {
            SECTION UI = "logo1.bmp"
            SECTION RAW = QcomPkg/Logo/Common/logo1.bmp
        }
        
      3. Flash imagefv after compiling the build.

        fastboot flash imagefv QcomPkg\SocPkg\[TARGET]\Bin\[LAA|LAB|WP]\[DEBUG|RELEASE]\imagefv.elf

        Note

        For other OSes this would be through mass storage or the emmcdl tool.

Mapping the display to the logo image file¶

Update property in QcomPkgSocPkg[TARGET]Commonuefiplat.cfg.

  1. Primary display:

    Set “PrimaryLogoIndex = 1” to use logo1.bmp.

  2. Secondary display:

    Set “SecondaryLogoIndex = 2” to use logo2.bmp, or set other index to use other logo.

    It is not mandatory to have unique logo bmp file per display, a previously used index may be reused.

Note

If these sections are missing then the default is to use logo1.bmp.


© Copyright 2024, Qualcomm Technologies, Inc. Last updated on Oct 08, 2024.

Built with Sphinx using a theme provided by Read the Docs.