BaseTools/BinToPcd: Fix Python 2.7.x compatibility issue
[mirror_edk2.git] / ArmVirtPkg / ArmVirtQemuKernel.fdf
CommitLineData
8de84d42
AB
1#\r
2# Copyright (c) 2011-2015, ARM Limited. All rights reserved.\r
3# Copyright (c) 2014, Linaro Limited. All rights reserved.\r
42e3d9eb 4# Copyright (c) 2015 - 2016, Intel Corporation. All rights reserved.\r
8de84d42
AB
5#\r
6# This program and the accompanying materials\r
7# are licensed and made available under the terms and conditions of the BSD License\r
8# which accompanies this distribution. The full text of the license may be found at\r
9# http://opensource.org/licenses/bsd-license.php\r
10#\r
11# THE PROGRAM IS DISTRIBUTED UNDER THE BSD LICENSE ON AN "AS IS" BASIS,\r
12# WITHOUT WARRANTIES OR REPRESENTATIONS OF ANY KIND, EITHER EXPRESS OR IMPLIED.\r
13#\r
14\r
15################################################################################\r
16#\r
17# FD Section\r
18# The [FD] Section is made up of the definition statements and a\r
19# description of what goes into the Flash Device Image. Each FD section\r
20# defines one flash "device" image. A flash device image may be one of\r
21# the following: Removable media bootable image (like a boot floppy\r
22# image,) an Option ROM image (that would be "flashed" into an add-in\r
23# card,) a System "Flash" image (that would be burned into a system's\r
24# flash) or an Update ("Capsule") image that will be used to update and\r
25# existing system flash.\r
26#\r
27################################################################################\r
28\r
29[FD.QEMU_EFI]\r
30BaseAddress = 0x00000000|gArmTokenSpaceGuid.PcdFdBaseAddress # QEMU assigns 0 - 0x8000000 for a BootROM\r
31Size = 0x00200000|gArmTokenSpaceGuid.PcdFdSize # The size in bytes of the FLASH Device\r
32ErasePolarity = 1\r
33\r
34# This one is tricky, it must be: BlockSize * NumBlocks = Size\r
35BlockSize = 0x00001000\r
36NumBlocks = 0x200\r
37\r
38################################################################################\r
39#\r
40# Following are lists of FD Region layout which correspond to the locations of different\r
41# images within the flash device.\r
42#\r
43# Regions must be defined in ascending order and may not overlap.\r
44#\r
45# A Layout Region start with a eight digit hex offset (leading "0x" required) followed by\r
46# the pipe "|" character, followed by the size of the region, also in hex with the leading\r
47# "0x" characters. Like:\r
48# Offset|Size\r
49# PcdOffsetCName|PcdSizeCName\r
50# RegionType <FV, DATA, or FILE>\r
51#\r
52################################################################################\r
53\r
54#\r
4d2ea261 55# Implement the Linux kernel header layout so that the loader will identify\r
8de84d42 56# it as something bootable, and execute it with a FDT pointer in x0 or r2.\r
4d2ea261 57# This area will be reused to store a copy of the FDT so round it up to 32 KB.\r
8de84d42 58#\r
4d2ea261 590x00000000|0x00008000\r
8de84d42
AB
60DATA = {\r
61!if $(ARCH) == AARCH64\r
62 0x01, 0x00, 0x00, 0x10, # code0: adr x1, .\r
4d2ea261 63 0xff, 0x1f, 0x00, 0x14, # code1: b 0x8000\r
8de84d42
AB
64 0x00, 0x00, 0x08, 0x00, 0x00, 0x00, 0x00, 0x00, # text_offset: 512 KB\r
65 0x00, 0x00, 0x20, 0x00, 0x00, 0x00, 0x00, 0x00, # image_size: 2 MB\r
66 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, # flags\r
67 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, # res2\r
68 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, # res3\r
69 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, # res4\r
70 0x41, 0x52, 0x4d, 0x64, # magic: "ARM\x64"\r
71 0x00, 0x00, 0x00, 0x00 # res5\r
72!else\r
73 0x08, 0x10, 0x4f, 0xe2, # adr r1, .\r
74 0x02, 0x00, 0xa0, 0xe1, # mov r0, r2 (DTB)\r
75 0x00, 0x00, 0xa0, 0xe1, # nop\r
76 0x00, 0x00, 0xa0, 0xe1, # nop\r
77 0x00, 0x00, 0xa0, 0xe1, # nop\r
78 0x00, 0x00, 0xa0, 0xe1, # nop\r
79 0x00, 0x00, 0xa0, 0xe1, # nop\r
80 0x00, 0x00, 0xa0, 0xe1, # nop\r
81\r
4d2ea261 82 0xf6, 0x1f, 0x00, 0xea, # b 0x8000\r
8de84d42
AB
83 0x18, 0x28, 0x6f, 0x01, # magic\r
84 0x00, 0x00, 0x00, 0x00, # start\r
85 0x00, 0x00, 0x20, 0x00, # image size: 2 MB\r
86 0x01, 0x02, 0x03, 0x04 # endiannness flag\r
87!endif\r
88}\r
89\r
4d2ea261 900x00008000|0x001f8000\r
8de84d42
AB
91gArmTokenSpaceGuid.PcdFvBaseAddress|gArmTokenSpaceGuid.PcdFvSize\r
92FV = FVMAIN_COMPACT\r
93\r
bf57a42a 94!include VarStore.fdf.inc\r
8de84d42
AB
95\r
96################################################################################\r
97#\r
98# FV Section\r
99#\r
100# [FV] section is used to define what components or modules are placed within a flash\r
101# device file. This section also defines order the components and modules are positioned\r
102# within the image. The [FV] section consists of define statements, set statements and\r
103# module statements.\r
104#\r
105################################################################################\r
106\r
c9eca0b2 107!include ArmVirtQemuFvMain.fdf.inc\r
8de84d42 108\r
8de84d42
AB
109[FV.FVMAIN_COMPACT]\r
110FvAlignment = 16\r
111ERASE_POLARITY = 1\r
112MEMORY_MAPPED = TRUE\r
113STICKY_WRITE = TRUE\r
114LOCK_CAP = TRUE\r
115LOCK_STATUS = TRUE\r
116WRITE_DISABLED_CAP = TRUE\r
117WRITE_ENABLED_CAP = TRUE\r
118WRITE_STATUS = TRUE\r
119WRITE_LOCK_CAP = TRUE\r
120WRITE_LOCK_STATUS = TRUE\r
121READ_DISABLED_CAP = TRUE\r
122READ_ENABLED_CAP = TRUE\r
123READ_STATUS = TRUE\r
124READ_LOCK_CAP = TRUE\r
125READ_LOCK_STATUS = TRUE\r
126\r
127 INF ArmVirtPkg/PrePi/ArmVirtPrePiUniCoreRelocatable.inf\r
128\r
129 FILE FV_IMAGE = 9E21FD93-9C72-4c15-8C4B-E77F1DB2D792 {\r
130 SECTION GUIDED EE4E5898-3914-4259-9D6E-DC7BD79403CF PROCESSING_REQUIRED = TRUE {\r
131 SECTION FV_IMAGE = FVMAIN\r
132 }\r
133 }\r
134\r
f4aee089 135!include ArmVirtRules.fdf.inc\r