I managed to do that yesterday, it is not hard to do, but it's not obvious to understand how it works. I am currently writing a short article/how to about it.
My main source is OSDev (http://wiki.osdev.org/UEFI). They use gnuefi, but it is easy to adapt to EDKII. The most difficult part is to get the Image Base address. You can have it by two ways: adding a little piece of code at the begining of your application, or by watching the debug lot. First way: add this lines at the beginning of your app: EFI_LOADED_IMAGE_PROTOCOL *LoadedImage; SystemTable->BootServices->HandleProtocol(ImageHandle, &gEfiLoadedImageProtocolGuid, (void **)&LoadedImage); Print(L"Image Base: %p\n", LoadedImage->ImageBase); Second way: use that command line to start OVMF with Qemu qemu-system-x86_64 -L . -s -hda fat:content/ -monitor stdio -debugcon file:debug.log -global isa-debugcon.iobase=0x402 Then, after the application is loaded, in the debug.log file, you will find this line: Loading driver at 0x0000620F000 EntryPoint=0x0000620F260 YourApp.efi Hope this will help. 2014-04-02 11:20 GMT+02:00 Roger <[email protected]>: > Anybody tried to use INTEL UEFI Development Kit Debugger Tool ? Can it > work in QEMU and OVMF environment? > > > -------------------------------- > Roger > > ----- 原始邮件 ----- > 发件人：Jordan Justen <[email protected]> > 收件人：[email protected], "[email protected]" < > [email protected]> > 主题：Re: [edk2] Source level debug using QEMU and OVMF > 日期：2014年03月29日 14点18分 > > > > ------------------------------------------------------------------------------ > > _______________________________________________ > edk2-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/edk2-devel > >
------------------------------------------------------------------------------
_______________________________________________ edk2-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/edk2-devel
