From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-lf0-x230.google.com (mail-lf0-x230.google.com [IPv6:2a00:1450:4010:c07::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id 7898B21DFA8FE for ; Thu, 30 Mar 2017 02:43:08 -0700 (PDT) Received: by mail-lf0-x230.google.com with SMTP id j90so22576299lfk.2 for ; Thu, 30 Mar 2017 02:43:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=cHj3j1dPhOW5DJjD/A+0RdDZi2ivVhGTdcFSGLt9pKU=; b=PGHSRoyF/OPokx5jEa7AMOb2LVfha3AEueN/sj44ILl+4uhEaMv5SbPKd7meCxscnD cDzWgAuvJN7eKGAeFvozTWcwFZghQmYFmh3u0y09E6PkHAIBBUJnJBfm78CW8MEWI7UY 25UQMzGKt768WHCNi2YW8bxAWh0Qa1fn31aiYFUfQoh0BurPGL6LINZCGH0LIX6GdKLR fgyzbA1Ptmrh0fkumenylKp17q+YJwxGquFUGPKtGX/Lqsmy5BdGwH+amYuUYuX7DzKU 8GGIGTzaMhNPZwCHaA8uphmu63LP+Q3sKmASGd3sCTFl6pWJkogAstV/qvD/w5voLG+V 5Kjg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=cHj3j1dPhOW5DJjD/A+0RdDZi2ivVhGTdcFSGLt9pKU=; b=LkY4lN2kJFEyJvlW73ycZ2s/LyXKxPP+re7pFjU6iGvrSzI7xPAtpmkvSBDLmyawqG BDKRxAQ/mFK9TJif9MXL1dhyYH3shJPEjBmKOTWAume97X9/jJfJyzoVzVnUPaqT3hNZ JGHbptWT7+UZzSlmTGratF/zQWqG+95D8FA57GjsDnR+XV+jgtRKnBVK5CRteXZ9ZfxJ ezFHP87NptnZ0FxnmtIJNYSKWTXjPfDy383YXYFyaMI2jyJ0Saam/Ns5WmdL4tBM3nTs iFySuxSPhnNEHeZctOmsemwahPyDhxxux0QL+xOZfhq3RdBDPQHiaPQtRuWCgMvEaMeW 1ZLA== X-Gm-Message-State: AFeK/H38sDGHtwknuS6z8l7wNCAGm3BT8CY2V6hUdiY70xyLaOEM3Sdl+9HnbOeKV4p/WBQe5cekfD7QqHQE5w== X-Received: by 10.25.233.24 with SMTP id g24mr1462932lfh.131.1490866986736; Thu, 30 Mar 2017 02:43:06 -0700 (PDT) MIME-Version: 1.0 Received: by 10.25.72.213 with HTTP; Thu, 30 Mar 2017 02:43:06 -0700 (PDT) In-Reply-To: References: <542CF652F8836A4AB8DBFAAD40ED192A4C5811AF@shsmsx102.ccr.corp.intel.com> From: Arka Sharma Date: Thu, 30 Mar 2017 15:13:06 +0530 Message-ID: To: "Fan, Jeff" Cc: "edk2-devel@lists.01.org" Subject: Re: Using Intel UDk debugger X-BeenThere: edk2-devel@lists.01.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: EDK II Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Mar 2017 09:43:09 -0000 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable I have also verified the null modem connection by booting to windows in my target pc, and I am able to break it in WinDbg. So the communication is ok. In the target system shell when I load the DebugAgentDxe it is not appeared in the "drivers -b". Also in my system the serial port is not managed by any driver initially. So I located it using "devices" and the issued "load -nc DebugAgentDxe.efi". Regards, Arka On Thu, Mar 30, 2017 at 2:27 PM, Arka Sharma wrote: > Thanks Jeff for your reply. I followed the steps as mentioned in "9.11 > Debugging a standalone module loaded in a UEFI shell". I have built > DebugAgentDxe and loaded it in my target system. I cross checked in my > target system UEFI setup Serial is enabled. In host I have installed > WinDbgX64 and UDK debugger. I have configured the debug port COM1, > connected the host and target with a null modem cable. Now when I > launch SoftDebugger WinDbg starts with an error message "Could not > start kernel debugging using > exdi:clsid=3D{F56FC1A6-3422-4320-A7F3-41EAEC2A367D} parameters. If I > attempt to reconnect with COM1 it throws "Access denied". Do I need to > enable something more in target system ? > > Regards, > Arka > > On Thu, Mar 30, 2017 at 10:55 AM, Fan, Jeff wrote: >> Arka, >> >> UDK Debugger tool supports your usage model. >> >> Please see the section "9.11 Debugging a standalone module loaded in a U= EFI shell" @ https://firmware.intel.com/sites/default/files/UDK_Debugger_To= ol_User_Manual_V1.11.pdf >> >> Thanks! >> Jeff >> -----Original Message----- >> From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of A= rka 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 WinD= bg and Intel UDK debugger. I want to debug a driver and an application on a= n Asrock borad, but going through the UDK debugger user manual I realize th= at 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 launch= ing 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 Asc= iiPrints. Is there any way to use DEBUG macro to redirect debug messages fr= om 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