Now EDKII SourceLevelDebug supports two physical channel: one is serial cable,
another is usb debug cable.
So if you have no EHCI debug port at your target machine, you can try serial
port.
If you want to use the COM2 of target machine, you need override
PcdSerialRegisterBase in MdeModulePkg.d
Jeff,
My current implementation starts earlier in PEI Core flow and was using the
call back function to allocate memory on the stack. Your example is quite a bit
father into PEI Core init. I modeled after DXE Core location, but I can't use a
global like in DXE, so I think I need the callback an
Andrew,
You remind me that GDB and WinDbg both set bp internally for some features,
like "run to line ###", "step out". It is too hard for end user of UDK Debugger
to know the details of Debugger implementation and avoid doing "bad" things
(run to line ###, or step out).
We need to clear the DR
Hi Feng
Your understanding of what I was trying to say, main usb port, was correct.
I was talking about EHCI usb debug port
I have one problem here. The problem is that none of the machines I have
here have EHCI debug port.
Now we are trying to debug using the COM2 (com1 is not working on this
mac
Neeraj
No. The current SourceLevelDebugPkg has no such DebugAgentDxe driver. It will
be released later, including the document.
Jeff
From: Neeraj Ladkani [mailto:nladk...@brocade.com]
Sent: Wednesday, August 29, 2012 12:03 AM
To: edk2-devel@lists.sourceforge.net
Subject: Re: [edk2] Using "Intel
Andrew,
Only the code before InitializeDebugAgent () cannot be debugged. Most of them
are core codes and most of platform developers needn't to debug it. If they
really wants to debug the such code, they could enable debugging from SEC
instead of PEI Core. As you mentioned, some architect does
That would be EFI_EXT_SCSI_PASS_THRU_PROTOCOL, but if the firmware does not
implement it, then you may be out of luck.
Thanks,
--Samer
From: Sushma Gurram [mailto:sushma.gur...@sandisk.com]
Sent: Tuesday, August 28, 2012 3:26 PM
To: edk2-devel@lists.sourceforge.net
Subject: Re: [edk2] SCSI Pro
Is there a standard way send SCSI commands to such devices? Can we use INT13
(AH=50h, AL=01h) - SendPacket function to issue SCSI commands?
My understanding is for such devices, we can issue SCSI commands only if Legacy
OpROM supports it and we need to understand the interface for the specific
O
Ray,
How do you know that the debugger does not automatically set breakpoints to
enable features? We have these kind of features in our debugger.
How do you clear the breakpoints? You need the debugger to stop prior to a
state change to clear the breakpoints, and to do this you you need the
Andrew,
In my opinion, if user sets software/hardware breakpoints and doesn't clear
them before booting to runtime. The result is undefined. User is responsible to
clear the breakpoints.
Thanks,
Ray
From: Andrew Fish [mailto:af...@apple.com]
Sent: Wednesday, August 29, 2012 12:21 AM
To: edk2-de
On Aug 28, 2012, at 9:21 AM, Andrew Fish wrote:
> Jeff,
>
> The location you note is very far into PEI Core Init. In the DXE Core the
> debugger is initialized right away, and in my local copy that is what I did
> in the PEI Core. Initing early implies you need to use InitializeDebugAgent
> (
Thanks Jeff,
Yes, that would be fine ! is current released "SourceLevelDebugPkg" has such
capabilities? if so , can you send some details on how this can be used?
Thanks
Neeraj
From: Fan, Jeff [mailto:jeff@intel.com]
Sent: Tuesday, August 28, 2012 9:18 PM
To: edk2-devel@lists.sourceforge.n
Jeff,
The location you note is very far into PEI Core Init. In the DXE Core the
debugger is initialized right away, and in my local copy that is what I did in
the PEI Core. Initing early implies you need to use InitializeDebugAgent ()
Function callback so the debugger context can be stored on t
Neeraj,
By now, SourceLevelDebugPkg has no such capability. We have planned to add one
new DebugAgentDxe driver into SourceLevelDebugPkg. Now, it was during test
procedure.
It could be loaded /unloaded in shell to enable/disable source debugging
feature. If enabled, you could source debugging
Hello All,
I am able to do source debugging using WinDBG on OVMF Package. is there any
mechanism using which we can do source debugging for my option rom (UEFI
driver) built with SourceLevelDebugPkg loaded on a real system which has
production system bios ( not built with SOURCE_DEBUG_ENABLE).
.
On 08/28/12 02:24, Jordan Justen wrote:
> Currently if SOURCE_DEBUG_ENABLE is enabled when building with
> GCC44, then the SEC module will not fit into SECFV.
>
> This change increases the size of SECFV to allow this.
>
> Contributed-under: TianoCore Contribution Agreement 1.0
> Signed-off-by: Jo
16 matches
Mail list logo
