From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-lf0-x229.google.com (mail-lf0-x229.google.com [IPv6:2a00:1450:4010:c07::229]) (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 81C5D21A0481E for ; Thu, 30 Mar 2017 18:40:09 -0700 (PDT) Received: by mail-lf0-x229.google.com with SMTP id z15so36508774lfd.1 for ; Thu, 30 Mar 2017 18:40:09 -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; bh=98ZzUOBCkdietSmyTITfecM2FxJEDdWEIqQxssLjHiI=; b=TCEw2qQA/Ud2HIx25BkO3NMyKkxs2bfbdLWh2qZ3k0B+JlaQttZpyW90F3OebemSSg NKgHCDphEP1xH8qL4uDp1+REJUAPNuNqdyS1u3gznW7+FE8wpbcuN2NlH+lvcqJUyx3z 9uDFOe32z/YJErrY32mMTKkmK8hmvv/8int9nofNbBj77e0oeicVgDHxjPuAKPJEGiei 9kegCWaK2BrPIxnYphvgEX+DOvHNQa9Yk+UFuhAvZ2GLb5BcAx17w5jdJWxHYCrX1Z2z GW95zZWOAiyGkZX98xK46yDQKKbGzcgtN+pgqy3gv4L/25SpnUxD8LKRKkNpAp5GyNOc /ViA== 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; bh=98ZzUOBCkdietSmyTITfecM2FxJEDdWEIqQxssLjHiI=; b=S+OHvE6v4dahfAeTKHHmhIORVGaXQTnc1RgSdy/43czw9FCPGmTEPSOinoyTqHxAGx X7A51ukXgYrxh98FR8MBIZ/ESEdGgj6myKIxgBIWFhbNtsdyakq02gqaLgGQeavHtNN6 Wq0Nke1KVeaA8CoAtqNljZbrvg+4JlA0OyHCyp1Z7ZktTkh5pMW0F84KqSTklruiQe4P 3Ghe4M/AGJbF9kwajm0yc7d6iwu7JXqOrAT7Ms+jnaCTQe95R0DIXjgxhzlL/cF2X3va +MODp/VYf/lia1NLTmd+IuiUwMu4v1i/BVJWByDqBiyr0VDlxHysptKail13/hSB3oyZ oVDw== X-Gm-Message-State: AFeK/H32k788Le09kOaLYYL8N35hY+xzmuhxK6PoJDImkihcUlXsyckNyrjbJQ4LwV3YVsGhmNzMRJ2z6DpZ9w== X-Received: by 10.25.228.66 with SMTP id b63mr121201lfh.177.1490924407725; Thu, 30 Mar 2017 18:40:07 -0700 (PDT) MIME-Version: 1.0 Received: by 10.25.72.213 with HTTP; Thu, 30 Mar 2017 18:40:07 -0700 (PDT) In-Reply-To: References: <542CF652F8836A4AB8DBFAAD40ED192A4C5811AF@shsmsx102.ccr.corp.intel.com> From: Arka Sharma Date: Fri, 31 Mar 2017 07:10:07 +0530 Message-ID: To: "Kinney, Michael D" Cc: "Fan, Jeff" , "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: Fri, 31 Mar 2017 01:40:10 -0000 Content-Type: text/plain; charset=UTF-8 Thanks a lot Mike. You are right. I have installed WinDbg 6.11.1404. Now the issue I mentioned earlier is not seen. But I am still not able to break into target system. I have loaded the DebugAgentDxe and loading was success. But in the shell I can find that still the serial port handle is not managed by any driver. Regards, Arka On Thu, Mar 30, 2017 at 9:28 PM, Kinney, Michael D wrote: > 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 Arka 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 >> >> 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={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_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 >> _______________________________________________ >> edk2-devel mailing list >> edk2-devel@lists.01.org >> https://lists.01.org/mailman/listinfo/edk2-devel