From: Laszlo Ersek <lersek@redhat.com>
To: "Kinney, Michael D" <michael.d.kinney@intel.com>,
wang xiaofeng <winggundum82@163.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 21:37:01 +0200 [thread overview]
Message-ID: <077448df-35eb-47c9-3fe7-09d6fe921f9a@redhat.com> (raw)
In-Reply-To: <E92EE9817A31E24EB0585FDF735412F5A7D73E70@ORSMSX113.amr.corp.intel.com>
On 08/09/17 20:21, Kinney, Michael D wrote:
> Laszlo,
>
> I works really well for me using QEMU on Windows.
>
> * Build OVMF setting -D SOURCE_DEBUG_ENABLE and -D DEBUG_ON_SERIAL_PORT.
>
> * Configure The UDK Debugger SoftDebugger.ini file to use TCP port 20716
>
> [Debug Port]
> Channel = TCP
> Server = localhost
> Port = 20716
>
> * Configure QEMU so the monitor and serial port
> are redirected to a tcp ports 20717 and 20716.
>
> -monitor tcp:localhost:20717,server
> -serial tcp:localhost:20716,server
>
> I use a batch file to launch the UDK debugger and
> and terminal emulators immediately before running
> QEMU because the tcp server in QEMU will
> timeout of a connect does not happen quickly.
>
> start "Monitor" /B "c:\Program Files (x86)\teraterm\ttermpro.exe" localhost:20717 /nossh
> start "Debugger" /B "C:\Program Files (x86)\Intel\Intel(R) UEFI Development Kit Debugger Tool\eXdi.exe" /LaunchWinDbg
> start "Console" /B "c:\Program Files (x86)\teraterm\ttermpro.exe" localhost:20715 /nossh
>
> start "QEMU" /B "%QEMU_PATH%\qemu-system-i386w.exe" ^
> -machine q35,smm=on,accel=tcg -cpu Nehalem ^
> -global ICH9-LPC.disable_s3=1 ^
> -drive if=pflash,format=raw,unit=0,file=%EDKII_BUILD_OUTPUT%\FV\OVMF_CODE.fd,readonly=on ^
> -drive if=pflash,format=raw,unit=1,file=%EDKII_BUILD_OUTPUT%\FV\OVMF_VARS.fd ^
> -monitor tcp:localhost:20717,server ^
> -serial tcp:localhost:20716,server
>
> Since the serial connections are redirected to tcp ports
> on the localhost, this actually provide an excellent
> UDK Debugger experience.
Thanks for the writeup. :) Maybe we should put this in the wiki
(although I'm completely aware of how I would react if this was
suggested to me in response to an email of mine :) )
And, perhaps I should give this another try sometime :)
Thank you!
Laszlo
next prev parent reply other threads:[~2017-08-09 19:34 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
2017-08-09 18:21 ` Kinney, Michael D
2017-08-09 19:37 ` Laszlo Ersek [this message]
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=077448df-35eb-47c9-3fe7-09d6fe921f9a@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