From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-lf0-x22e.google.com (mail-lf0-x22e.google.com [IPv6:2a00:1450:4010:c07::22e]) (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 E870D21A04820 for ; Thu, 30 Mar 2017 19:13:59 -0700 (PDT) Received: by mail-lf0-x22e.google.com with SMTP id j90so36774433lfk.2 for ; Thu, 30 Mar 2017 19:13:59 -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=FFZ0Cg5bElSpTjzh5aeeDjj0jbYpSwBTRv/w9CIhAzg=; b=GMyT71NRnnjO46ZWTs0g6arpU2dKOhb96z527lfaPz4F5RkKicTwxtaatj2mgIy7X5 jOqbblJENXAX8ZOWC/lDLfuZ3foxjcV7oEEPLyCX7RE2IPhV23bGkBmtGHsu0novNZ2o wJ//omM9SEqM9FjTcLRyFwWX4rL0r79VmUUwFIWM/Mwo5G4fZ6pgpsyKGY1wv0RrR2gv dxYseXfmF/3fiQFRwAR/IrljKijKCmZx4KSCXVGW1ZQqk5MDUkf29oFoXLOupSLb5wI0 SLoMqNXC1EyyGLK4aHATpK70a2BzG8cTGuEJNHY9rJw9RuG7OMjn/+Za1UkGage2n9Ig 5wmw== 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=FFZ0Cg5bElSpTjzh5aeeDjj0jbYpSwBTRv/w9CIhAzg=; b=V9Z001Vt+f/4uNFu8kGOMF3G4+b1kFPO203UOdm2ua5ufGXLuuNgoLVvmIyupR4n4t Q/jWnjnMxG/zBS7W8AihTwUH54+90YIwuu5J2E01wNM78T6elUJp3LCnfQswbHPcMslN ZM1M3N3CQyp4xwF5dA4lej0/h9G5vy2kxlGKi4xXqA+1Bv+AxIor2TbOf2Jv9udCqJ+U ebUL2Je8lYi1LwsEpNZT9eRk/rMUXHYxgfsvDCL7b+mrqe/w7Bwr8NlwmKVlkanTNLaw pK6RAhiiI+wKlVXYqNh3nGklQ0qasNPGSqLjD0MpA/UjqtzKCepONBt02Jd8yWO58ik8 ltOg== X-Gm-Message-State: AFeK/H360Evs7iSw8m+PcyUuCUFjfwOGdklxZIukgwwTelmj8N/GfRMdQyx1oB+GvfpwRu5x053VhWjzL9e9oQ== X-Received: by 10.25.150.74 with SMTP id y71mr128802lfd.167.1490926438235; Thu, 30 Mar 2017 19:13:58 -0700 (PDT) MIME-Version: 1.0 Received: by 10.25.72.213 with HTTP; Thu, 30 Mar 2017 19:13:57 -0700 (PDT) In-Reply-To: <542CF652F8836A4AB8DBFAAD40ED192A4C582311@shsmsx102.ccr.corp.intel.com> References: <542CF652F8836A4AB8DBFAAD40ED192A4C5811AF@shsmsx102.ccr.corp.intel.com> <542CF652F8836A4AB8DBFAAD40ED192A4C582311@shsmsx102.ccr.corp.intel.com> From: Arka Sharma Date: Fri, 31 Mar 2017 07:43:57 +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: Fri, 31 Mar 2017 02:14:00 -0000 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable When I load DebugAgentDxe I get cF=C3=83=C3=97=C3=BF?k=C3=A4=C3=BF=C3=BF=C3= =BF=C3=A3+=C3=BE in putty. Also when I boot to shell there is not IsaSerialDxe or any other driver managing the serial port. I manually located the serial port with "devices". In the shell when I load DebugAgentDxe I get the same text as mentioned in Step 8 of section 9.11 in UDK_Debugger_Tool_User_Manual_V1.11.pdf. And the load status is success. Regards, Arka On Fri, Mar 31, 2017 at 7:19 AM, Fan, Jeff wrote: > DebugAgentDxe will consume Serial Port to setup debug channel with HOST. > > Please shutdown the UDK debug HOST software and use any serial tool (Like= putty). Are there any output when you load DebugAgentDxe in shell? Could = you paste here? > > You need to make sure the DebugAgentDxe used the correct serial port para= meter on your platform. > > Thanks! > Jeff > > -----Original Message----- > From: Arka Sharma [mailto:arka.sw1988@gmail.com] > Sent: Friday, March 31, 2017 9:40 AM > To: Kinney, Michael D > Cc: Fan, Jeff; edk2-devel@lists.01.org > Subject: Re: [edk2] Using Intel UDk debugger > > 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 n= ot 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 wr= ote: >>> > 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 wrot= e: >>> >> 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_M= anual_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 w= ell 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