From: Laszlo Ersek <lersek@redhat.com>
To: wang xiaofeng <winggundum82@163.com>,
Michael Kinney <michael.d.kinney@intel.com>
Cc: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: Qestion about how to debug OVMF with UDT on QEMU
Date: Wed, 9 Aug 2017 13:02:46 +0200 [thread overview]
Message-ID: <dc4a01de-606a-cb3d-31b2-e54384b1f1ae@redhat.com> (raw)
In-Reply-To: <622959b9.707d.15dc5ea41ee.Coremail.winggundum82@163.com>
On 08/09/17 09:34, wang xiaofeng wrote:
> Hello All,
> I try to debug OVMF with UDT on QEMU in windows.
> I build OVMF on windows 7 with VS2013 . And also runs it in QEMUWin32.
> I add DEFINE SOURCE_DEBUG_ENABLE = TRUE in ovmf.dsc and build a new bios. From makefile it seems this feature is enabled for OVMF SecMain
>
>
> $(BIN_DIR)\SourceLevelDebugPkg\Library\PeCoffExtraActionLibDebug\PeCoffExtraActionLibDebug\OUTPUT\PeCoffExtraActionLib.lib \
> $(BIN_DIR)\SourceLevelDebugPkg\Library\DebugAgent\SecPeiDebugAgentLib\OUTPUT\SecPeiDebugAgentLib.lib \
>
>
> But how can I link it to the local Windows UDT(which I have tested works for real hardware bios by serail port )?
> Another question is why OVMF fdf don;t include DebugAgentPei.inf?
> Or I have to enable at least 1 or 2 VM for this task?
> Thanks in advance!
In the past I've tried to set up the UDK debugger between two virtual
machines, using a UNIX domain socket to connect their serial ports. It
didn't work, the debugger protocol kept falling apart. I suspected that
the emulated serial ports didn't follow the timings of physical serial
ports closely enough.
So, I never use SOURCE_DEBUG_ENABLE, but I think others on the list may
have gotten it to work? Mike perhaps?
Thanks
Laszlo
next prev parent reply other threads:[~2017-08-09 11:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-09 7:34 Qestion about how to debug OVMF with UDT on QEMU wang xiaofeng
2017-08-09 11:02 ` Laszlo Ersek [this message]
2017-08-09 18:21 ` Kinney, Michael D
2017-08-09 19:37 ` Laszlo Ersek
2017-08-10 5:50 ` wang xiaofeng
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=dc4a01de-606a-cb3d-31b2-e54384b1f1ae@redhat.com \
--to=devel@edk2.groups.io \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox