<html>
<head>
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
</head>
<body>
<div class="moz-cite-prefix">
<div class="moz-cite-prefix">(Sending again, first mail was
bounced off, sorry if someone receives this for a second time)<br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">Thanks, I wish I knew about this
earlier, this is indeed a great aid in debugging. It is even
worth waiting for a couple of hours to (re)build the image :)</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">As for my problem, it is solved now.
The immediate cause was bad global PHY offset in RC_CONFIG0
register. I tried to get fancy and hardcode values from
talos-MEMD.tvpd before we had implemented VPD parser and I must
have downloaded wrong file, as the values in it don't make
sense. Now I can't even find the exact version of file in
repository, so probably I accidentally overwrote it with
garbage.</div>
<div class="moz-cite-prefix"><br>
</div>
Thank you again, this definitely pushed us forward.</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">On 09.04.2021 21:04, Daniel M Crowell
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:OF7DC09029.BC4A6A74-ON862586B2.00689BE6-862586B2.0068C04C@notes.na.collabserv.com">
<meta http-equiv="content-type" content="text/html;
charset=windows-1252">
<p><font size="2">> No, I haven't. How can I get it?</font></p>
<p><font size="2">> > Have you attempted to get a complete
scom trace from the original Hostboot code and compare it to
your new code? That is a pretty typical debug strategy on our
side when migrating from the initial hardware bringup scripts
into the firmware implementation.</font><br>
<br>
<font size="2">For the Hostboot side of things you can enable
console traces out to the console with this change in your
<system>.config file</font><br>
<font size="2"> set CONSOLE_OUTPUT_TRACE</font><br>
<font size="2"> </font><br>
<font size="2"> </font><br>
<font size="2">To enable full scom tracing, change this
TRACSCOMP into a TRACFCOMP</font><br>
<font size="2"> </font><a
href="https://github.com/open-power/hostboot/blob/59772b9569e74080cd6294f076be53fdf7db9db6/src/include/usr/fapi2/fapiPlatTrace.H#L74"
moz-do-not-send="true"><u><font size="2" color="#0000FF">https://github.com/open-power/hostboot/blob/59772b9569e74080cd6294f076be53fdf7db9db6/src/include/usr/fapi2/fapiPlatTrace.H#L74</font></u></a><br>
<font size="2">Or you can change the attribute value
(HB_SETTINGS. traceScanDebug) that enables it if you want to
bound it.</font><br>
<font size="2"> </font><a
href="https://github.com/open-power/hostboot/blob/59772b9569e74080cd6294f076be53fdf7db9db6/src/usr/targeting/common/xmltohb/attribute_types.xml#L2134"
moz-do-not-send="true"><u><font size="2" color="#0000FF">https://github.com/open-power/hostboot/blob/59772b9569e74080cd6294f076be53fdf7db9db6/src/usr/targeting/common/xmltohb/attribute_types.xml#L2134</font></u></a><br>
<font size="2"> </font><br>
<font size="2">Warning - your are going to see A LOT of output,
so pipe it out to a file somewhere.</font><br>
<font size="2"><br>
--<br>
Dan Crowell<br>
Senior Software Engineer - Power Systems Enablement Firmware<br>
<a class="moz-txt-link-abbreviated" href="mailto:dcrowell@us.ibm.com">dcrowell@us.ibm.com</a></font><br>
</p>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
OpenPower-Firmware mailing list
<a class="moz-txt-link-abbreviated" href="mailto:OpenPower-Firmware@lists.ozlabs.org">OpenPower-Firmware@lists.ozlabs.org</a>
<a class="moz-txt-link-freetext" href="https://lists.ozlabs.org/listinfo/openpower-firmware">https://lists.ozlabs.org/listinfo/openpower-firmware</a>
</pre>
</blockquote>
<p><br>
</p>
<pre class="moz-signature" cols="72">--
Krystian Hebel
Firmware Engineer
<a class="moz-txt-link-freetext" href="https://3mdeb.com">https://3mdeb.com</a> | @3mdeb_com</pre>
</body>
</html>