From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-lf0-x22c.google.com (mail-lf0-x22c.google.com [IPv6:2a00:1450:4010:c07::22c]) (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 3825C21DFA7A8 for ; Fri, 31 Mar 2017 02:18:16 -0700 (PDT) Received: by mail-lf0-x22c.google.com with SMTP id z15so40448046lfd.1 for ; Fri, 31 Mar 2017 02:18:16 -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=63o7WuvAXZCs3dkcEz/FHn7OVmkz6OjqossMMz7Kb2o=; b=ZQ+pIKWyUUJBCvSHhkqPPxdtgzZhCUEPtWHAfNIA4urUy/NrNuAJJxaVVHxYeqQZ67 y0nLlaSdyVBRLZuMCjvWlluYS1WUHr9ccx6+9Di2vae1u23MI7/bz2vtWZXUUF6MgotS 1/IHofeaCkKTkaCEwJEcwym80K2bxB2cfnxieRy2nTAwpZpovyNx7UZwnIp1t+fV/Kdp lnJ/U6Ng4uM1ucBmP8fWq683350Sqt1L0t1ipl1W5YoDY3vkNcrz4LM9XT7tL++677Jz tPw4Hqg36mUD4lm3l6o43O7ApWbAE6jzXnQpMGGlnIUSyCQwoFzN1SJIOnI60M7xgKGB 0X+Q== 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=63o7WuvAXZCs3dkcEz/FHn7OVmkz6OjqossMMz7Kb2o=; b=QuJF6JkC5CD6+GySzFPxgPiseWDxDRWgaToVxwg1CKodVvtXNFB3ImAASI+IxUTi7T 9NXEe9KjU+xyPmz/2nudwtFiwX9JaXV0IUrzG9tCo1qwVmuGsbmB7JVJeVCRIrZ/YEZK AujZbfP9RqUBvVxI6Pj2SPE8N5x2nxqQQBVE/Q0E472q3E7u92Mun7/X8VkPQLSs5cp4 +jQOZ1JlJw5ZJgsdju91PrjyLlztIF0h0hsLkrzb0gApbgwtpdIVRtTtrWi3u4+lqMvm VlWA0JzwIjp4FjGS2DAFyCg3+uyejhGVjTE7+zp536G0wayoLs/5+vDIAI4VNA98XsAK 8F9g== X-Gm-Message-State: AFeK/H0s5U0RyEFlt9A4Ao99P39snT7Wq3R3EG8G/lZsBdOgZ3WZ1/eOwFIdCLnIf9sp5MIalv2G6rlGgRrlgQ== X-Received: by 10.25.233.24 with SMTP id g24mr651365lfh.131.1490951894508; Fri, 31 Mar 2017 02:18:14 -0700 (PDT) MIME-Version: 1.0 Received: by 10.25.72.213 with HTTP; Fri, 31 Mar 2017 02:18:13 -0700 (PDT) In-Reply-To: <542CF652F8836A4AB8DBFAAD40ED192A4C582AAE@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> <542CF652F8836A4AB8DBFAAD40ED192A4C58254C@shsmsx102.ccr.corp.intel.com> <542CF652F8836A4AB8DBFAAD40ED192A4C582AAE@shsmsx102.ccr.corp.intel.com> From: Arka Sharma Date: Fri, 31 Mar 2017 14:48:13 +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 09:18:16 -0000 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Thanks Jeff. Using CpuBreakPoint() has temporarily solved the purpose. But I need the symbols to be loaded properly. Please let me know if I missed something in building the application. As mentioned earlier I have disabled optimization and used --keepexceptiontable in GenFw. Is there something else I need to do. Regards, Arka On Fri, Mar 31, 2017 at 12:58 PM, Fan, Jeff wrote: > It seems that symbols are not load correctly. > > Could you add CpuBreakpoint () in your application code to trigger SW bre= akpoint by code instead of setting unresolved breakpoint by Windbg? And to = check if it could break at CpuBreakpoint() and symbols if could be loaded c= orrectly. > > Jeff > -----Original Message----- > From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of Ar= ka Sharma > Sent: Friday, March 31, 2017 2:53 PM > To: Fan, Jeff > Cc: edk2-devel@lists.01.org > Subject: Re: [edk2] Using Intel UDk debugger > > I have built my application with /Od and /Oy-, and GENFW_FLAGS as --keepe= xceptiontable. After loading DebugAgentDxe I have set an unresolved breakpo= int in main routine of my application, but when I start my application in t= he target no breakpoint is hit. But when the application crashes the symbol= s are properly loaded in WinDbg and the asm code for the crash is displayed= . > > Regards, > Arka > > On Fri, Mar 31, 2017 at 9:03 AM, Fan, Jeff wrote: >> Yes. >> >> If you want to enable flow control, you could set gEfiMdeModulePkgTokenS= paceGuid.PcdSerialUseHardwareFlowControl|TRUE in SourceLevelDebugPkg.dsc wh= en you build DebugAgentDxe.efi. >> >> It could improve the serial port communication quality. >> >> Thanks! >> Jeff >> >> -----Original Message----- >> From: Arka Sharma [mailto:arka.sw1988@gmail.com] >> Sent: Friday, March 31, 2017 11:23 AM >> To: Fan, Jeff >> Cc: edk2-devel@lists.01.org >> Subject: Re: [edk2] Using Intel UDk debugger >> >> Thanks a lot Jeff. Setting FlowControl to 0 worked. Now I am able to bre= ak into the target system. Just wondering is it same as mentioned in UDK_De= bugger_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 ho= st 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 Debu= gAgentDxe 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 Arka 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= break 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 = failed! 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= \Library\BaseSerialPortLib16550\BaseSerialPortLib16550.inf to read/write da= ta from serial port. >>>> >>>> SerialPortLib|MdeModulePkg/Library/BaseSerialPortLib16550/BaseSerial >>>> SerialPortLib|P >>>> SerialPortLib|o >>>> 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= setting. >>>> >>>> When DebugAgentDxe is loaded, we expected the following words could be= output from serial port. >>>> "Send INIT break packet and try to connect the HOST (Intel(R) UDK De= bugger 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 Isa= SerialDxe or any other driver managing the serial port. I manually located = the serial port with "devices". In the shell when I load DebugAgentDxe I ge= t 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 HO= ST. >>>>> >>>>> Please shutdown the UDK debug HOST software and use any serial tool (= Like putty). Are there any output when you load DebugAgentDxe in shell? Co= uld you paste here? >>>>> >>>>> You need to make sure the DebugAgentDxe used the correct serial port = parameter 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 abl= e 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=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_Us= er_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 thi= s 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 > _______________________________________________ > edk2-devel mailing list > edk2-devel@lists.01.org > https://lists.01.org/mailman/listinfo/edk2-devel