From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-lf0-x231.google.com (mail-lf0-x231.google.com [IPv6:2a00:1450:4010:c07::231]) (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 E99A421A04826 for ; Thu, 30 Mar 2017 20:22:44 -0700 (PDT) Received: by mail-lf0-x231.google.com with SMTP id z15so37155141lfd.1 for ; Thu, 30 Mar 2017 20:22:44 -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=89ZTFTLyEY3fm9uqkKMkZmXOeME5ip9ueZ+EfoDKKPI=; b=Pn31HgXHqyzErLwSFGEMu0kTUVGwBDRm4XLKDV9/kOAHuLRFDCMWN1gXZXyROOBqia YZcW+hz4GcBhw8X8Q/mi80/7AfK/UpLDr8l1wumipKLDnJH+W7USCy3dOZ247tEvEPpO MtN0zkxfp7rBydtpPnHW1PcTl1D2AH/1B7DKOA3VsEUDHfnFf0jvTHKJs19Jqqu6atFA e7Y7V6cmWAQWJRKgSHVMaWeccR/jcRtGmjvoQmBcWoEd2BCJwOe0jcCoKrzpAAXXxUo+ WMQbRC4i7t5NDecl5t0sLnc4rxFhCDgVOTW4Csra4II5GHg/p9tMmXxXSo2E8NePBB78 bMTA== 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=89ZTFTLyEY3fm9uqkKMkZmXOeME5ip9ueZ+EfoDKKPI=; b=lnk8IfXnqD569fNjoSQNx8WIOueW+xmBs+rhDNfVi5qYTyO2PzKDEAHjX3jmrhupLk zm9/fMtxIOw4G63lvMZwxgo1jclxMp+sMaKulJlHBDIELEF7yPMq6IbAtgn3rSZbacIe V2BQV4MWIN+vrkWzXMaoKWYFNFPqZc9oqPS6mOdHJ/kYCQgQ2vUg3RvsnwuQxukHib25 OXlC+Eq5UGYab4tQK2ii41PMTxr+f3Z3F7UnFRP+MwlF2EE5ep8UXNzbG3cKErQ+v68N q9iuuYeCHKapjgpiN+JjzjVVLsgNLvwOaoKICjgS3s2M78dlO5CsdFdN3wxOS4T2JVPm 1iug== X-Gm-Message-State: AFeK/H1loJdQtAtvE2QZPtlWeHFV8wL4oBrXeQgGeuhPXsfPzW7sf93swc241Wqhc3yBpAmjWKFN8Bn7VJ/n0g== X-Received: by 10.46.22.11 with SMTP id w11mr223292ljd.68.1490930562642; Thu, 30 Mar 2017 20:22:42 -0700 (PDT) MIME-Version: 1.0 Received: by 10.25.72.213 with HTTP; Thu, 30 Mar 2017 20:22:41 -0700 (PDT) In-Reply-To: <542CF652F8836A4AB8DBFAAD40ED192A4C5824BE@shsmsx102.ccr.corp.intel.com> References: <542CF652F8836A4AB8DBFAAD40ED192A4C5811AF@shsmsx102.ccr.corp.intel.com> <542CF652F8836A4AB8DBFAAD40ED192A4C582311@shsmsx102.ccr.corp.intel.com> <542CF652F8836A4AB8DBFAAD40ED192A4C582422@shsmsx102.ccr.corp.intel.com> <542CF652F8836A4AB8DBFAAD40ED192A4C5824BE@shsmsx102.ccr.corp.intel.com> From: Arka Sharma Date: Fri, 31 Mar 2017 08:52:41 +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 03:22:45 -0000 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Thanks a lot Jeff. Setting FlowControl to 0 worked. Now I am able to break into the target system. Just wondering is it same as mentioned in UDK_Debugger_Tool_User_Manual_V1.11.pdf 2.2.3.2 "If the platform-specific Serial Port Library does not support hardware flow control, flow control on the host machine should be turned off as well." Regards, Arka On Fri, Mar 31, 2017 at 8:23 AM, Fan, Jeff wrote: > It's good start. Please drop the putty from now. > > Please check the following setting in SoftDebugger.ini on HOST side, and = change FlowControl to 0 and change Trace to 0x10 > > [Debug Port] > Channel =3D Serial > Port =3D COM1 > FlowControl =3D 0 > BaudRate =3D 115200 > Server =3D > > [Maintenance] > ; Uncomment the below line to turn on tracing > Trace=3D0x10 > > You could start intel UDK debugger tool on HOST side and then load DebugA= gentDxe on target side. If you still cannot connect Windbg, please send me= udk-debugger-trace.log file under C:\User\xxx\. > > Thanks! > Jeff > > -----Original Message----- > From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of Ar= ka Sharma > Sent: Friday, March 31, 2017 10:45 AM > To: Fan, Jeff > Cc: edk2-devel@lists.01.org > Subject: Re: [edk2] Using Intel UDk debugger > > After changing the putty settings I am getting this message "Send INIT b= reak packet and try to connect the HOST (Intel(R) UDK Debugger Tool v1.5)" = followed by =C3=BE?Y=C2=BA=C3=BE?Y=C2=BA=C3=BE?Y=C2=BAHOST connection is fa= iled! Am I missing some other settings ? > > Regards, > Arka > > On Fri, Mar 31, 2017 at 7:58 AM, Fan, Jeff wrote: >> It's better if there is no Serial driver to manage the serial port. >> >> DebugAgentDxe built from SourceLevelDebugPkg is consuming MdeModulePkg\L= ibrary\BaseSerialPortLib16550\BaseSerialPortLib16550.inf to read/write data= from serial port. >> >> SerialPortLib|MdeModulePkg/Library/BaseSerialPortLib16550/BaseSerialPo >> rtLib16550.inf >> >> It's default Serial port parameters are: BaudRate:115200, Data: 8 bit, = Parity: none, Stop: 1 bit, Flow control: none Please check your putty COM s= etting. >> >> When DebugAgentDxe is loaded, we expected the following words could be o= utput from serial port. >> "Send INIT break packet and try to connect the HOST (Intel(R) UDK Debu= gger Tool v1.5)" >> >> Thanks! >> Jeff >> >> -----Original Message----- >> From: Arka Sharma [mailto:arka.sw1988@gmail.com] >> Sent: Friday, March 31, 2017 10:14 AM >> To: Fan, Jeff >> Cc: edk2-devel@lists.01.org >> Subject: Re: [edk2] Using Intel UDk debugger >> >> 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 IsaSer= ialDxe 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 t= he same text as mentioned in Step 8 of section 9.11 in UDK_Debugger_Tool_Us= er_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 (Li= ke putty). Are there any output when you load DebugAgentDxe in shell? Coul= d you paste here? >>> >>> You need to make sure the DebugAgentDxe used the correct serial port pa= rameter 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 wa= s 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=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 wr= ote: >>>>> >> 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 > _______________________________________________ > edk2-devel mailing list > edk2-devel@lists.01.org > https://lists.01.org/mailman/listinfo/edk2-devel