<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Unknown SECO event on IMX8.QM in i.MX Processors</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/Unknown-SECO-event-on-IMX8-QM/m-p/1357684#M181755</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;thank you for your reply. We followed&lt;/P&gt;&lt;P&gt;&lt;A href="https://source.codeaurora.org/external/imx/uboot-imx/tree/doc/imx/ahab/guides/mx8_mx8x_secure_boot.txt?h=imx_v2020.04_5.4.70_2.3.0" target="_blank"&gt;https://source.codeaurora.org/external/imx/uboot-imx/tree/doc/imx/ahab/guides/mx8_mx8x_secure_boot.txt?h=imx_v2020.04_5.4.70_2.3.0&lt;/A&gt;&lt;/P&gt;&lt;P&gt;since the IMX8.QM uses AHAB (in contrast to HABv4).&lt;/P&gt;&lt;P&gt;Regards,&lt;BR /&gt;David&lt;/P&gt;</description>
    <pubDate>Tue, 19 Oct 2021 07:26:53 GMT</pubDate>
    <dc:creator>ddroe</dc:creator>
    <dc:date>2021-10-19T07:26:53Z</dc:date>
    <item>
      <title>Unknown SECO event on IMX8.QM</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Unknown-SECO-event-on-IMX8-QM/m-p/1354714#M181455</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;we're encountering the SECO event 0x00DAF429 on all our IMX8.QM boards. This is the U-Boot output:&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;=&amp;gt; ahab_status
Lifecycle: 0x0020, NXP closed

SECO Event[0] = 0x00DAF429
sc_seco_get_event: idx: 1, res:3&lt;/LI-CODE&gt;&lt;P&gt;I could not find any documentation of that event. It occurs independently of key fuses being burnt or not.&lt;/P&gt;&lt;P&gt;I also supsect it to prevent us from closing the device since:&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;=&amp;gt; ahab_close
Warning: Please ensure your sample is in NXP closed state, OEM SRK hash has been fused,
         and you are able to boot a signed image successfully without any SECO events reported.
         If not, your sample will be unrecoverable.

Really perform this operation? &amp;lt;y/N&amp;gt;
y
sc_seco_forward_lifecycle: change:16, res:11
Error in forward lifecycle to OEM closed
exit not allowed from main input shell.&lt;/LI-CODE&gt;&lt;P&gt;If anyone knows what the event means and how it needs to be handled, that would be of great help. Thank you!&lt;/P&gt;&lt;P&gt;Cheers,&lt;/P&gt;&lt;P&gt;David&lt;/P&gt;</description>
      <pubDate>Wed, 13 Oct 2021 07:17:44 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Unknown-SECO-event-on-IMX8-QM/m-p/1354714#M181455</guid>
      <dc:creator>ddroe</dc:creator>
      <dc:date>2021-10-13T07:17:44Z</dc:date>
    </item>
    <item>
      <title>Re: Unknown SECO event on IMX8.QM</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Unknown-SECO-event-on-IMX8-QM/m-p/1357589#M181747</link>
      <description>&lt;P&gt;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/192369"&gt;@ddroe&lt;/a&gt;&amp;nbsp;&lt;BR /&gt;Hello,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&amp;nbsp; have You followed recommendations of U-boot help, regarding secure image building &lt;BR /&gt;and deployment?&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://source.codeaurora.org/external/imx/uboot-imx/tree/doc/imx/habv4/guides?h=imx_v2020.04_5.4.70_2.3.0" target="_blank"&gt;https://source.codeaurora.org/external/imx/uboot-imx/tree/doc/imx/habv4/guides?h=imx_v2020.04_5.4.70_2.3.0&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards,&lt;BR /&gt;Yuri.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 19 Oct 2021 05:19:53 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Unknown-SECO-event-on-IMX8-QM/m-p/1357589#M181747</guid>
      <dc:creator>Yuri</dc:creator>
      <dc:date>2021-10-19T05:19:53Z</dc:date>
    </item>
    <item>
      <title>Re: Unknown SECO event on IMX8.QM</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Unknown-SECO-event-on-IMX8-QM/m-p/1357684#M181755</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;thank you for your reply. We followed&lt;/P&gt;&lt;P&gt;&lt;A href="https://source.codeaurora.org/external/imx/uboot-imx/tree/doc/imx/ahab/guides/mx8_mx8x_secure_boot.txt?h=imx_v2020.04_5.4.70_2.3.0" target="_blank"&gt;https://source.codeaurora.org/external/imx/uboot-imx/tree/doc/imx/ahab/guides/mx8_mx8x_secure_boot.txt?h=imx_v2020.04_5.4.70_2.3.0&lt;/A&gt;&lt;/P&gt;&lt;P&gt;since the IMX8.QM uses AHAB (in contrast to HABv4).&lt;/P&gt;&lt;P&gt;Regards,&lt;BR /&gt;David&lt;/P&gt;</description>
      <pubDate>Tue, 19 Oct 2021 07:26:53 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Unknown-SECO-event-on-IMX8-QM/m-p/1357684#M181755</guid>
      <dc:creator>ddroe</dc:creator>
      <dc:date>2021-10-19T07:26:53Z</dc:date>
    </item>
    <item>
      <title>Re: Unknown SECO event on IMX8.QM</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Unknown-SECO-event-on-IMX8-QM/m-p/1357749#M181758</link>
      <description>&lt;P&gt;Hi David,&lt;/P&gt;
&lt;P&gt;Which version of SCFW / SECO FW are you using ?&lt;/P&gt;
&lt;P&gt;If you have a pending SECO event, the SECO will refuse to close your part.&lt;/P&gt;
&lt;P&gt;Best regards,&lt;/P&gt;
&lt;P&gt;Seb&lt;/P&gt;</description>
      <pubDate>Tue, 19 Oct 2021 08:29:42 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Unknown-SECO-event-on-IMX8-QM/m-p/1357749#M181758</guid>
      <dc:creator>seb_haezebrouck</dc:creator>
      <dc:date>2021-10-19T08:29:42Z</dc:date>
    </item>
    <item>
      <title>Re: Unknown SECO event on IMX8.QM</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Unknown-SECO-event-on-IMX8-QM/m-p/1357866#M181768</link>
      <description>&lt;P&gt;Hi Seb,&lt;/P&gt;&lt;P&gt;it's&lt;/P&gt;&lt;PRE&gt;&lt;SPAN&gt;SCFW &lt;/SPAN&gt;bc122ee1&lt;SPAN&gt;, SECO-FW d63fdb21, IMX-MKIMAGE 8947fea3, ATF 2a26786&lt;/SPAN&gt;&lt;/PRE&gt;&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Regards,&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;David&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 19 Oct 2021 11:28:28 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Unknown-SECO-event-on-IMX8-QM/m-p/1357866#M181768</guid>
      <dc:creator>ddroe</dc:creator>
      <dc:date>2021-10-19T11:28:28Z</dc:date>
    </item>
    <item>
      <title>Re: Unknown SECO event on IMX8.QM</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Unknown-SECO-event-on-IMX8-QM/m-p/1357906#M181773</link>
      <description>&lt;P&gt;OK - this means: SECO FW QM B0 revision 3.7.4, SCFW revision 2020q4_p3.&lt;/P&gt;
&lt;P&gt;You should move to SECO FW 3.8.1 / SCFW 2020q4_p4 at least, if you are using&amp;nbsp;&lt;SPAN&gt;Linux 5.4.70_2.3.x release (e.g. switch to Linux 5.4.70_2.3.4).&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;This is available from nxp.com: SCFW porting kit version 1.7.4.&lt;/P&gt;
&lt;P&gt;From the SCFW 2020q4_p4 release notes (included in SCFW 1.7.4 porting kit):&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="seb_haezebrouck_0-1634645779854.png" style="width: 999px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/159509iA24473666B1BA38C/image-size/large?v=v2&amp;amp;px=999" role="button" title="seb_haezebrouck_0-1634645779854.png" alt="seb_haezebrouck_0-1634645779854.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;Seb&lt;/P&gt;</description>
      <pubDate>Tue, 19 Oct 2021 13:21:14 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Unknown-SECO-event-on-IMX8-QM/m-p/1357906#M181773</guid>
      <dc:creator>seb_haezebrouck</dc:creator>
      <dc:date>2021-10-19T13:21:14Z</dc:date>
    </item>
    <item>
      <title>Re: Unknown SECO event on IMX8.QM</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Unknown-SECO-event-on-IMX8-QM/m-p/1357913#M181777</link>
      <description>&lt;P&gt;Ok, thanks for the hint, I'll try a more recent FW.&lt;/P&gt;</description>
      <pubDate>Tue, 19 Oct 2021 12:42:35 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Unknown-SECO-event-on-IMX8-QM/m-p/1357913#M181777</guid>
      <dc:creator>ddroe</dc:creator>
      <dc:date>2021-10-19T12:42:35Z</dc:date>
    </item>
    <item>
      <title>Re: Unknown SECO event on IMX8.QM</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Unknown-SECO-event-on-IMX8-QM/m-p/1359251#M181865</link>
      <description>&lt;P&gt;Successfully tested closing the device with a more recent FW. Thanks again!&lt;/P&gt;</description>
      <pubDate>Thu, 21 Oct 2021 07:06:06 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Unknown-SECO-event-on-IMX8-QM/m-p/1359251#M181865</guid>
      <dc:creator>ddroe</dc:creator>
      <dc:date>2021-10-21T07:06:06Z</dc:date>
    </item>
    <item>
      <title>Re: Unknown SECO event on IMX8.QM</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Unknown-SECO-event-on-IMX8-QM/m-p/1359500#M181901</link>
      <description>&lt;P&gt;Maybe I should add that the problem was not caused by an outdated SECO-FW but either by an outdated SCFW or the combination of SECO-FW and SCFW. We have used the same SECO-FW in both attempts but only with a more recent SCFW, closing the device succeeded.&lt;/P&gt;</description>
      <pubDate>Thu, 21 Oct 2021 12:33:37 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Unknown-SECO-event-on-IMX8-QM/m-p/1359500#M181901</guid>
      <dc:creator>ddroe</dc:creator>
      <dc:date>2021-10-21T12:33:37Z</dc:date>
    </item>
  </channel>
</rss>

