From: "Fan, Jeff" <jeff.fan@intel.com>
To: Arka Sharma <arka.sw1988@gmail.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: Using Intel UDk debugger
Date: Thu, 30 Mar 2017 05:25:13 +0000 [thread overview]
Message-ID: <542CF652F8836A4AB8DBFAAD40ED192A4C5811AF@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <CAPO=kN0yHCuNuQCiAH37SDodne3nrOL2tkg+-q5=aM34Xs5RAg@mail.gmail.com>
Arka,
UDK Debugger tool supports your usage model.
Please see the section "9.11 Debugging a standalone module loaded in a UEFI shell" @ https://firmware.intel.com/sites/default/files/UDK_Debugger_Tool_User_Manual_V1.11.pdf
Thanks!
Jeff
-----Original Message-----
From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of Arka Sharma
Sent: Thursday, March 30, 2017 1:15 PM
To: edk2-devel@lists.01.org
Subject: [edk2] Using Intel UDk debugger
Hi,
I am sorry if it is not a right place to ask this. I have installed WinDbg and Intel UDK debugger. I want to debug a driver and an application on an Asrock borad, but going through the UDK debugger user manual I realize that SourceLevelDebugPkg has to be included in target firmware image. Now in this case what option do I have to proceed with the debugging ? I am launching my application from shell and in the shell post codes are disabled, the application code get stuck randomly. So far I was trying to debug with AsciiPrints. Is there any way to use DEBUG macro to redirect debug messages from UEFI driver as well as application to some serial port in this case ?
Regards,
Arka
_______________________________________________
edk2-devel mailing list
edk2-devel@lists.01.org
https://lists.01.org/mailman/listinfo/edk2-devel
next prev parent reply other threads:[~2017-03-30 5:25 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-30 5:14 Using Intel UDk debugger Arka Sharma
2017-03-30 5:25 ` Fan, Jeff [this message]
2017-03-30 8:57 ` Arka Sharma
2017-03-30 9:43 ` Arka Sharma
2017-03-30 15:58 ` Kinney, Michael D
2017-03-31 1:40 ` Arka Sharma
2017-03-31 1:49 ` Fan, Jeff
2017-03-31 2:13 ` Arka Sharma
2017-03-31 2:28 ` Fan, Jeff
2017-03-31 2:44 ` Arka Sharma
2017-03-31 2:53 ` Fan, Jeff
2017-03-31 3:22 ` Arka Sharma
2017-03-31 3:33 ` Fan, Jeff
2017-03-31 6:53 ` Arka Sharma
2017-03-31 7:28 ` Fan, Jeff
2017-03-31 9:18 ` Arka Sharma
[not found] ` <734D49CCEBEEF84792F5B80ED585239D5B8F62B6@SHSMSX104.ccr.corp.intel.com>
2017-04-01 8:56 ` Arka Sharma
2017-04-02 1:56 ` Ni, Ruiyu
2017-04-05 9:53 ` Arka Sharma
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=542CF652F8836A4AB8DBFAAD40ED192A4C5811AF@shsmsx102.ccr.corp.intel.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