<html><body><p><font size="2">> No, I haven't. How can I get it?</font><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"><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"><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>dcrowell@us.ibm.com</font><BR>
</body></html>