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-boun...@lists.01.org] On Behalf Of Arka > Sharma > Sent: Thursday, March 30, 2017 2:43 AM > To: Fan, Jeff <jeff....@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.sw1...@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....@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-boun...@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
