<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal">H<span style="color:#1F497D">ello</span>,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I faced a very strange behavior of the DS-5 debugger when I debug AARCH64 UEFI with the latest
<o:p></o:p></p>
<p class="MsoNormal">(well, the one which contains <o:p></o:p></p>
<p class="MsoNormal"><span style="font-family:"Courier New","serif"">DEFINE GCC_DLINK2_FLAGS_COMMON = --script=$(EDK_TOOLS_PATH)/Scripts/GccBase.lds<o:p></o:p></span></p>
<p class="MsoNormal">)<br>
tools_def.template.<o:p></o:p></p>
<p class="MsoNormal">Whenever I step in the debugger it never matches the source where the execution point currently is.<o:p></o:p></p>
<p class="MsoNormal">It is impossible to step-by-step debug with this…<o:p></o:p></p>
<p class="MsoNormal">If I switch to the older tools_def.template, I don’t have those issues, and can debug with no problem.<o:p></o:p></p>
<p class="MsoNormal">However, the ShellPkg cannot be built with older tools_def.template if I want to have ShellPkg (New Shell) instead of ShellBinPkg.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Please advise if I am doing anything wrong?<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">This is how I debug if step-by-step debug is needed:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I place a while(1) in a place of interest. Build UEFI, and then reboot the board and run the uefi; then when it reaches the point of while1,
<o:p></o:p></p>
<p class="MsoNormal">I connect DS-5 to the device and execute <o:p></o:p></p>
<p class="MsoNormal">ArmPlatformPkg/Scripts/Ds5/cmd_load_symbols.py -f (0x85000000,0x00280000) -m (0x80000000,0x40000000) –a<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">And expect to be at the (while1 line). With the latest tools_def.tempalte the source point is weird; with the previous ones – OK.<o:p></o:p></p>
<p class="MsoNormal">Any advice would be appreciated.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thank you,<o:p></o:p></p>
<p class="MsoNormal">Vladimir<o:p></o:p></p>
</div>
</body>
</html>