> On May 30, 2016, at 12:26 AM, Li Hongcheng <[email protected]> wrote: > > Hello everyone, > My name is Owen and I am a senior student from Renmin University of China. > Recently I used a tool named UEFI Extract to parse my UEFI ROM file. There is > a “info.txt” file for every DXE PE file, and many of these “info.txt” files > contains a item called “Data memory address”, which is a 32-bit hexadecimal > with a format of “FF******h”.
On an x86 PC the reset vector if 0xFFFFFFF0 and that is usually at the end of the ROM. So it sounds like you are getting ROM addresses. > I referred to 《DXE CIS v0.9》 and other UEFI related specifications but could > not find any useful information which explains the “Data memory address”. I > guess it is the location that PE files would be loaded into memory, but > cannot find any solid prove. EFI uses PE/COFF images that are relocatable. They are generally linked at (or near) zero and they are relocated when they are loaded into memory. For the very early code in the ROM it must execute from the ROM and in the edk2 the builds relocate the PE/COFF image to the address it will execute from the ROM. Thanks, Andrew Fish > If you happen to know the answer to my problem, please shed some lights on > me, I would really appreciated that. Thank you very much. > 发送自 Windows 10 版邮件<https://go.microsoft.com/fwlink/?LinkId=550986>应用 > > _______________________________________________ > edk2-devel mailing list > [email protected] > https://lists.01.org/mailman/listinfo/edk2-devel _______________________________________________ edk2-devel mailing list [email protected] https://lists.01.org/mailman/listinfo/edk2-devel
