What is the largest space of the rom?? I want build the OVMF.fd with SECURE_BOOT_ENABLE and I have changed the size and offset in OvmfPkg/OvmfPkgX64.fdf,but the qemu couldn't use it to boot a VM.Why?
------------------ ???????? ------------------
??????: "Olivier Martin";
????????: 2013??6??17??(??????) ????5:53
??????: "Kirkendall, Garrett";"edk2-devel@lists.sourceforge.net";
????: Re: [edk2] ArmPlatformPkg/ArmVExpressPkg/ArmVExpress-RTSM-*.fdf FDlayout
mistake???
You are right. I have just fixed the size of the ARM RTSM FD files (svn rev
14426).
Thanks for the feedback,
Olivier
From: Kirkendall, Garrett [mailto:garrett.kirkend...@amd.com]
Sent: 12 June 2013 23:01
To: edk2-devel@lists.sourceforge.net
Subject: [edk2] ArmPlatformPkg/ArmVExpressPkg/ArmVExpress-RTSM-*.fdf FD layout
mistake???
I was looking through the ArmPlatformPkg/ArmVExpressPkg/ArmVExpress-RTSM-*.fdf
files, and there looks like an FD section anomaly.
The Size variable is set to 0x00280000, but the regions add up to 0x00300000.
What size is really intended? Too bad the tools don??t catch this kind of
thing.
Size = 0x00280000|gArmTokenSpaceGuid.PcdFdSize # The size in
bytes of the FLASH Device
Offset |Size
0x00000000|0x00080000
0x00080000|0x00280000
Full FD section from one file:
[FD.RTSM_VE_Cortex-A9_EFI]
BaseAddress = 0x08000000|gArmTokenSpaceGuid.PcdFdBaseAddress # The base
address of the Firmware in NOR Flash.
Size = 0x00280000|gArmTokenSpaceGuid.PcdFdSize # The size in
bytes of the FLASH Device
ErasePolarity = 1
# This one is tricky, it must be: BlockSize * NumBlocks = Size
BlockSize = 0x00001000
NumBlocks = 0x280
################################################################################
#
# Following are lists of FD Region layout which correspond to the locations of
different
# images within the flash device.
#
# Regions must be defined in ascending order and may not overlap.
#
# A Layout Region start with a eight digit hex offset (leading "0x" required)
followed by
# the pipe "|" character, followed by the size of the region, also in hex with
the leading
# "0x" characters. Like:
# Offset|Size
# PcdOffsetCName|PcdSizeCName
# RegionType <FV, DATA, or FILE>
#
################################################################################
0x00000000|0x00080000
gArmTokenSpaceGuid.PcdSecureFvBaseAddress|gArmTokenSpaceGuid.PcdSecureFvSize
FV = FVMAIN_SEC
0x00080000|0x00280000
gArmTokenSpaceGuid.PcdFvBaseAddress|gArmTokenSpaceGuid.PcdFvSize
FV = FVMAIN_COMPACT
Garrett Kirkendall
SMTS Firmware Engineer
AMD Technology & Engineering
7171 Southwest Parkway
Austin, TX, 78735
U.S.A.
O: +(1) 512 602 3255
Visit us at: Facebook | amd.com
-- IMPORTANT NOTICE: The contents of this email and any attachments are
confidential and may also be privileged. If you are not the intended recipient,
please notify the sender immediately and do not disclose the contents to any
other person, use it for any purpose, or store or copy the information in any
medium. Thank you.<<56C3FDA4@57955027.3AE4BE51.jpg>>
------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev
_______________________________________________ edk2-devel mailing list edk2-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/edk2-devel
