[mirror_edk2.git] / ArmVirtPkg / ArmVirtQemu.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
# UEFI has trouble dealing with FVs that reside at physical address 0x0.\r
# So instead, put a hardcoded 'jump to 0x1000' at offset 0x0, and put the\r
# real FV at offset 0x1000\r
#\r
0x00000000|0x00001000\r
DATA = {\r
!if $(ARCH) == AARCH64\r
  0x00, 0x04, 0x00, 0x14   # 'b 0x1000' in AArch64 ASM\r
!else\r
  0xfe, 0x03, 0x00, 0xea   # 'b 0x1000' in AArch32 ASM\r
!endif\r
}\r
\r
0x00001000|0x001ff000\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 ArmPlatformPkg/PrePeiCore/PrePeiCoreUniCore.inf\r
  INF MdeModulePkg/Core/Pei/PeiMain.inf\r
  INF ArmPlatformPkg/PlatformPei/PlatformPeim.inf\r
  INF ArmPlatformPkg/MemoryInitPei/MemoryInitPeim.inf\r
  INF ArmPkg/Drivers/CpuPei/CpuPei.inf\r
  INF MdeModulePkg/Universal/PCD/Pei/Pcd.inf\r
  INF MdeModulePkg/Universal/Variable/Pei/VariablePei.inf\r
  INF MdeModulePkg/Core/DxeIplPeim/DxeIpl.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
Commit	Line	Data
6f5872b1	1	#\r
7fbd1eb2	2	# Copyright (c) 2011-2015, ARM Limited. All rights reserved.\r
6f5872b1	3	# Copyright (c) 2014, Linaro Limited. All rights reserved.\r
42e3d9eb	4	# Copyright (c) 2015 - 2016, Intel Corporation. All rights reserved.\r
6f5872b1	5	#\r
9792fb0e	6	# SPDX-License-Identifier: BSD-2-Clause-Patent\r
6f5872b1 MC	7	#\r
	8	\r
	9	################################################################################\r
	10	#\r
	11	# FD Section\r
	12	# The [FD] Section is made up of the definition statements and a\r
	13	# description of what goes into the Flash Device Image. Each FD section\r
	14	# defines one flash "device" image. A flash device image may be one of\r
	15	# the following: Removable media bootable image (like a boot floppy\r
	16	# image,) an Option ROM image (that would be "flashed" into an add-in\r
	17	# card,) a System "Flash" image (that would be burned into a system's\r
	18	# flash) or an Update ("Capsule") image that will be used to update and\r
	19	# existing system flash.\r
	20	#\r
	21	################################################################################\r
	22	\r
	23	[FD.QEMU_EFI]\r
	24	BaseAddress = 0x00000000\|gArmTokenSpaceGuid.PcdFdBaseAddress # QEMU assigns 0 - 0x8000000 for a BootROM\r
	25	Size = 0x00200000\|gArmTokenSpaceGuid.PcdFdSize # The size in bytes of the FLASH Device\r
	26	ErasePolarity = 1\r
	27	\r
	28	# This one is tricky, it must be: BlockSize * NumBlocks = Size\r
	29	BlockSize = 0x00001000\r
	30	NumBlocks = 0x200\r
	31	\r
	32	################################################################################\r
	33	#\r
	34	# Following are lists of FD Region layout which correspond to the locations of different\r
	35	# images within the flash device.\r
	36	#\r
	37	# Regions must be defined in ascending order and may not overlap.\r
	38	#\r
	39	# A Layout Region start with a eight digit hex offset (leading "0x" required) followed by\r
	40	# the pipe "\|" character, followed by the size of the region, also in hex with the leading\r
	41	# "0x" characters. Like:\r
	42	# Offset\|Size\r
	43	# PcdOffsetCName\|PcdSizeCName\r
	44	# RegionType <FV, DATA, or FILE>\r
	45	#\r
	46	################################################################################\r
	47	\r
	48	#\r
	49	# UEFI has trouble dealing with FVs that reside at physical address 0x0.\r
	50	# So instead, put a hardcoded 'jump to 0x1000' at offset 0x0, and put the\r
	51	# real FV at offset 0x1000\r
	52	#\r
	53	0x00000000\|0x00001000\r
	54	DATA = {\r
	55	!if $(ARCH) == AARCH64\r
	56	0x00, 0x04, 0x00, 0x14 # 'b 0x1000' in AArch64 ASM\r
	57	!else\r
	58	0xfe, 0x03, 0x00, 0xea # 'b 0x1000' in AArch32 ASM\r
	59	!endif\r
	60	}\r
	61	\r
	62	0x00001000\|0x001ff000\r
	63	gArmTokenSpaceGuid.PcdFvBaseAddress\|gArmTokenSpaceGuid.PcdFvSize\r
	64	FV = FVMAIN_COMPACT\r
	65	\r
bf57a42a	66	!include VarStore.fdf.inc\r
6f5872b1 MC	67	\r
	68	################################################################################\r
	69	#\r
	70	# FV Section\r
	71	#\r
	72	# [FV] section is used to define what components or modules are placed within a flash\r
	73	# device file. This section also defines order the components and modules are positioned\r
	74	# within the image. The [FV] section consists of define statements, set statements and\r
	75	# module statements.\r
	76	#\r
	77	################################################################################\r
	78	\r
c9eca0b2	79	!include ArmVirtQemuFvMain.fdf.inc\r
26a36374	80	\r
6f5872b1 MC	81	[FV.FVMAIN_COMPACT]\r
	82	FvAlignment = 16\r
	83	ERASE_POLARITY = 1\r
	84	MEMORY_MAPPED = TRUE\r
	85	STICKY_WRITE = TRUE\r
	86	LOCK_CAP = TRUE\r
	87	LOCK_STATUS = TRUE\r
	88	WRITE_DISABLED_CAP = TRUE\r
	89	WRITE_ENABLED_CAP = TRUE\r
	90	WRITE_STATUS = TRUE\r
	91	WRITE_LOCK_CAP = TRUE\r
	92	WRITE_LOCK_STATUS = TRUE\r
	93	READ_DISABLED_CAP = TRUE\r
	94	READ_ENABLED_CAP = TRUE\r
	95	READ_STATUS = TRUE\r
	96	READ_LOCK_CAP = TRUE\r
	97	READ_LOCK_STATUS = TRUE\r
	98	\r
6f5872b1 MC	99	INF ArmPlatformPkg/PrePeiCore/PrePeiCoreUniCore.inf\r
	100	INF MdeModulePkg/Core/Pei/PeiMain.inf\r
	101	INF ArmPlatformPkg/PlatformPei/PlatformPeim.inf\r
	102	INF ArmPlatformPkg/MemoryInitPei/MemoryInitPeim.inf\r
	103	INF ArmPkg/Drivers/CpuPei/CpuPei.inf\r
	104	INF MdeModulePkg/Universal/PCD/Pei/Pcd.inf\r
	105	INF MdeModulePkg/Universal/Variable/Pei/VariablePei.inf\r
	106	INF MdeModulePkg/Core/DxeIplPeim/DxeIpl.inf\r
	107	\r
	108	FILE FV_IMAGE = 9E21FD93-9C72-4c15-8C4B-E77F1DB2D792 {\r
	109	SECTION GUIDED EE4E5898-3914-4259-9D6E-DC7BD79403CF PROCESSING_REQUIRED = TRUE {\r
	110	SECTION FV_IMAGE = FVMAIN\r
	111	}\r
	112	}\r
	113	\r
f4aee089	114	!include ArmVirtRules.fdf.inc\r