Since the configuration header never changes unless the board parameters
in ConfigurationHeader.dat are updated, we can take a snapshot of the
binary and add it to the FDF definition. This way, it will get emitted
by the EDK2 build system instead of having to use a separate
post-processing tool to add it to the flash image.
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Reviewed-by: Leif Lindholm <leif.lindholm@linaro.org>
git-svn-id: https://svn.code.sf.net/p/edk2/code/trunk/edk2@18210
6f19259b-4bc3-4df7-8a09-
765794883524
\r
\r
[FD.BeagleBoard_EFI]\r
-BaseAddress = 0x80008000|gArmTokenSpaceGuid.PcdFdBaseAddress #The base address of the FLASH Device.\r
+BaseAddress = 0x80007DF8|gArmTokenSpaceGuid.PcdFdBaseAddress #The base address of the FLASH Device.\r
Size = 0x000B0000|gArmTokenSpaceGuid.PcdFdSize #The size in bytes of the FLASH Device\r
ErasePolarity = 1\r
BlockSize = 0x1\r
# RegionType <FV, DATA, or FILE>\r
#\r
################################################################################\r
-0x00000000|0x000B0000\r
+0x00000000|0x00000200\r
+FILE = BeagleBoardPkg/ConfigurationHeader.bin\r
+\r
+0x00000200|0x00000008\r
+DATA = {\r
+ 0xF8, 0xFD, 0x0A, 0x00, # image size: 0xB0000 - 0x208 == 0xAFDF8\r
+ 0x00, 0x80, 0x00, 0x80 # entry point: 0x80008000\r
+}\r
+\r
+0x00000208|0x000AFDF8\r
gArmTokenSpaceGuid.PcdFvBaseAddress|gArmTokenSpaceGuid.PcdFvSize\r
FV = FVMAIN_COMPACT\r
\r