From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga04.intel.com (mga04.intel.com [192.55.52.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id 33A9721DFA7B0 for ; Thu, 30 Mar 2017 08:58:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=intel.com; i=@intel.com; q=dns/txt; s=intel; t=1490889498; x=1522425498; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=wr2o3ERx3NwML+HogxHItatLvxvQQNTK7KBob6MJO0A=; b=E5M+Gk1yguI4nMq3EhJnjvjmr9gTj6T/9kblSJo2adQfil2UAQHi0jyL twkspzObdnikGiUsMDGRI2m5u1iZAQ==; Received: from fmsmga004.fm.intel.com ([10.253.24.48]) by fmsmga104.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 30 Mar 2017 08:58:17 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.36,247,1486454400"; d="scan'208";a="242103812" Received: from orsmsx101.amr.corp.intel.com ([10.22.225.128]) by fmsmga004.fm.intel.com with ESMTP; 30 Mar 2017 08:58:17 -0700 Received: from orsmsx159.amr.corp.intel.com (10.22.240.24) by ORSMSX101.amr.corp.intel.com (10.22.225.128) with Microsoft SMTP Server (TLS) id 14.3.319.2; Thu, 30 Mar 2017 08:58:17 -0700 Received: from orsmsx113.amr.corp.intel.com ([169.254.9.59]) by ORSMSX159.amr.corp.intel.com ([169.254.11.95]) with mapi id 14.03.0319.002; Thu, 30 Mar 2017 08:58:16 -0700 From: "Kinney, Michael D" To: Arka Sharma , "Fan, Jeff" , "Kinney, Michael D" CC: "edk2-devel@lists.01.org" Thread-Topic: [edk2] Using Intel UDk debugger Thread-Index: AQHSqRYddolaJx1xEEOcvJT8S4/unqGtiqKAgAAMmwD///MCcA== Date: Thu, 30 Mar 2017 15:58:16 +0000 Message-ID: References: <542CF652F8836A4AB8DBFAAD40ED192A4C5811AF@shsmsx102.ccr.corp.intel.com> In-Reply-To: Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ctpclassification: CTP_IC x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiM2ZjYmIyNzktN2QyZC00NWI4LWI0NWUtMGRiNmFkMzAxMjVhIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX0lDIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE1LjkuNi42IiwiVHJ1c3RlZExhYmVsSGFzaCI6IjBwMk5VMCs4NXlZdlZkRlVQVWVqNEVZYzdBSVBQNkYwdjhYSzBKdzRNZGc9In0= x-originating-ip: [10.22.254.140] MIME-Version: 1.0 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 15:58:18 -0000 Content-Language: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi Arka, I have seen that error when the wrong version of WinDbg is used. What version of WinDbg did you install? Does it match the version listed in the UDK Debugger manual? Mike > -----Original Message----- > From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of Ar= ka Sharma > Sent: Thursday, March 30, 2017 2:43 AM > To: Fan, Jeff > Cc: edk2-devel@lists.01.org > Subject: Re: [edk2] Using Intel UDk debugger >=20 > 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". >=20 > Regards, > Arka >=20 > On Thu, Mar 30, 2017 at 2:27 PM, Arka Sharma wrot= e: > > 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= UEFI > shell" @ > https://firmware.intel.com/sites/default/files/UDK_Debugger_Tool_User_Man= ual_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 Wi= nDbg and > Intel UDK debugger. I want to debug a driver and an application on an Asr= ock borad, > but going through the UDK debugger user manual I realize that SourceLevel= DebugPkg > 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. S= o 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 s= erial port > in this case ? > >> > >> Regards, > >> Arka > >> _______________________________________________ > >> edk2-devel mailing list > >> edk2-devel@lists.01.org > >> https://lists.01.org/mailman/listinfo/edk2-devel > _______________________________________________ > edk2-devel mailing list > edk2-devel@lists.01.org > https://lists.01.org/mailman/listinfo/edk2-devel