Re: Using Intel UDk debugger

[Arka Sharma <arka.sw1988@gmail.com>]

When I load DebugAgentDxe I get cFÃ×ÿ?käÿÿÿã+þ 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 <jeff.fan@intel.com> 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 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 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 <michael.d.kinney@intel.com> 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 <jeff.fan@intel.com>
>>> 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 <arka.sw1988@gmail.com> 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 <jeff.fan@intel.com> 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