10.01.2015 Views

Intel(r) UEFI Development Kit Debugger Tool User Manual

Intel(r) UEFI Development Kit Debugger Tool User Manual

Intel(r) UEFI Development Kit Debugger Tool User Manual

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Caution: Each time the firmware image is rebuilt, the source-level debug package must be<br />

included. If the debug package is not included, the <strong>Intel</strong> UDK <strong>Debugger</strong> <strong>Tool</strong> cannot<br />

be used to debug the target firmware.<br />

2. Program—Program the firmware image into flash memory on the target system.<br />

3. Launch and debug—On the host system, launch a debugger that includes the<br />

functionality added by the <strong>Intel</strong> UDK <strong>Debugger</strong> <strong>Tool</strong>.<br />

Figure 5-1—Building a firmware image with the source-level debug package.<br />

The source-level debug package in the firmware build must be included each time<br />

the firmware image is built.<br />

5.4 Using the WinDbg-based debug solution<br />

On a Windows platform, the <strong>Intel</strong> UDK <strong>Debugger</strong> <strong>Tool</strong> allows:<br />

Debugging of source-level code.<br />

Debugging as early as late SEC (the security phase), after temporary RAM<br />

set up, for the normal boot path.<br />

The start of debugging system management mode (SMM) code by stopping<br />

the target at the next system management interrupt (SMI).<br />

Setting of unresolved breakpoints.<br />

Late attach<br />

5.4.1 Start a WinDbg debug session from SEC<br />

Follow these steps to start a WinDbg session:<br />

1. Launch “Start WinDbg using UDK <strong>Debugger</strong> <strong>Tool</strong>” from<br />

Windows Start -> All Programs -> <strong>Intel</strong> UDK <strong>Debugger</strong> <strong>Tool</strong>.<br />

25

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!