BaseTools:Change the path of the file that Binary Cache

[mirror_edk2.git] / ArmVirtPkg / ArmVirtQemuKernel.fdf

#\r
#  Copyright (c) 2011-2015, ARM Limited. All rights reserved.\r
#  Copyright (c) 2014, Linaro Limited. All rights reserved.\r
#  Copyright (c) 2015 - 2016, Intel Corporation. All rights reserved.\r
#\r
#  SPDX-License-Identifier: BSD-2-Clause-Patent\r
#\r
\r
################################################################################\r
#\r
# FD Section\r
# The [FD] Section is made up of the definition statements and a\r
# description of what goes into  the Flash Device Image.  Each FD section\r
# defines one flash "device" image.  A flash device image may be one of\r
# the following: Removable media bootable image (like a boot floppy\r
# image,) an Option ROM image (that would be "flashed" into an add-in\r
# card,) a System "Flash"  image (that would be burned into a system's\r
# flash) or an Update ("Capsule") image that will be used to update and\r
# existing system flash.\r
#\r
################################################################################\r
\r
[FD.QEMU_EFI]\r
BaseAddress   = 0x00000000|gArmTokenSpaceGuid.PcdFdBaseAddress  # QEMU assigns 0 - 0x8000000 for a BootROM\r
Size          = 0x00200000|gArmTokenSpaceGuid.PcdFdSize         # The size in bytes of the FLASH Device\r
ErasePolarity = 1\r
\r
# This one is tricky, it must be: BlockSize * NumBlocks = Size\r
BlockSize     = 0x00001000\r
NumBlocks     = 0x200\r
\r
################################################################################\r
#\r
# Following are lists of FD Region layout which correspond to the locations of different\r
# images within the flash device.\r
#\r
# Regions must be defined in ascending order and may not overlap.\r
#\r
# A Layout Region start with a eight digit hex offset (leading "0x" required) followed by\r
# the pipe "|" character, followed by the size of the region, also in hex with the leading\r
# "0x" characters. Like:\r
# Offset|Size\r
# PcdOffsetCName|PcdSizeCName\r
# RegionType <FV, DATA, or FILE>\r
#\r
################################################################################\r
\r
#\r
# Implement the Linux kernel header layout so that the loader will identify\r
# it as something bootable, and execute it with a FDT pointer in x0 or r2.\r
# This area will be reused to store a copy of the FDT so round it up to 32 KB.\r
#\r
0x00000000|0x00008000\r
DATA = {\r
!if $(ARCH) == AARCH64\r
  0x01, 0x00, 0x00, 0x10,                         # code0: adr x1, .\r
  0xff, 0x1f, 0x00, 0x14,                         # code1: b 0x8000\r
  0x00, 0x00, 0x08, 0x00, 0x00, 0x00, 0x00, 0x00, # text_offset: 512 KB\r
  0x00, 0x00, 0x20, 0x00, 0x00, 0x00, 0x00, 0x00, # image_size: 2 MB\r
  0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, # flags\r
  0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, # res2\r
  0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, # res3\r
  0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, # res4\r
  0x41, 0x52, 0x4d, 0x64,                         # magic: "ARM\x64"\r
  0x00, 0x00, 0x00, 0x00                          # res5\r
!else\r
  0x08, 0x10, 0x4f, 0xe2, # adr r1, .\r
  0x02, 0x00, 0xa0, 0xe1, # mov r0, r2 (DTB)\r
  0x00, 0x00, 0xa0, 0xe1, # nop\r
  0x00, 0x00, 0xa0, 0xe1, # nop\r
  0x00, 0x00, 0xa0, 0xe1, # nop\r
  0x00, 0x00, 0xa0, 0xe1, # nop\r
  0x00, 0x00, 0xa0, 0xe1, # nop\r
  0x00, 0x00, 0xa0, 0xe1, # nop\r
\r
  0xf6, 0x1f, 0x00, 0xea, # b 0x8000\r
  0x18, 0x28, 0x6f, 0x01, # magic\r
  0x00, 0x00, 0x00, 0x00, # start\r
  0x00, 0x00, 0x20, 0x00, # image size: 2 MB\r
  0x01, 0x02, 0x03, 0x04  # endiannness flag\r
!endif\r
}\r
\r
0x00008000|0x001f8000\r
gArmTokenSpaceGuid.PcdFvBaseAddress|gArmTokenSpaceGuid.PcdFvSize\r
FV = FVMAIN_COMPACT\r
\r
!include VarStore.fdf.inc\r
\r
################################################################################\r
#\r
# FV Section\r
#\r
# [FV] section is used to define what components or modules are placed within a flash\r
# device file.  This section also defines order the components and modules are positioned\r
# within the image.  The [FV] section consists of define statements, set statements and\r
# module statements.\r
#\r
################################################################################\r
\r
!include ArmVirtQemuFvMain.fdf.inc\r
\r
[FV.FVMAIN_COMPACT]\r
FvAlignment        = 16\r
ERASE_POLARITY     = 1\r
MEMORY_MAPPED      = TRUE\r
STICKY_WRITE       = TRUE\r
LOCK_CAP           = TRUE\r
LOCK_STATUS        = TRUE\r
WRITE_DISABLED_CAP = TRUE\r
WRITE_ENABLED_CAP  = TRUE\r
WRITE_STATUS       = TRUE\r
WRITE_LOCK_CAP     = TRUE\r
WRITE_LOCK_STATUS  = TRUE\r
READ_DISABLED_CAP  = TRUE\r
READ_ENABLED_CAP   = TRUE\r
READ_STATUS        = TRUE\r
READ_LOCK_CAP      = TRUE\r
READ_LOCK_STATUS   = TRUE\r
\r
  INF ArmVirtPkg/PrePi/ArmVirtPrePiUniCoreRelocatable.inf\r
\r
  FILE FV_IMAGE = 9E21FD93-9C72-4c15-8C4B-E77F1DB2D792 {\r
    SECTION GUIDED EE4E5898-3914-4259-9D6E-DC7BD79403CF PROCESSING_REQUIRED = TRUE {\r
      SECTION FV_IMAGE = FVMAIN\r
    }\r
  }\r
\r
!include ArmVirtRules.fdf.inc\r