<?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: imx8qxp-mek secure boot arm64 binary in i.MX Processors</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/imx8qxp-mek-secure-boot-arm64-binary/m-p/1764924#M216468</link>
    <description>&lt;P&gt;&lt;SPAN&gt;Debian currently does not support this, but it may be supported in the future.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Regards&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Harvey&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Tue, 28 Nov 2023 12:47:48 GMT</pubDate>
    <dc:creator>Harvey021</dc:creator>
    <dc:date>2023-11-28T12:47:48Z</dc:date>
    <item>
      <title>imx8qxp-mek secure boot arm64 binary</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/imx8qxp-mek-secure-boot-arm64-binary/m-p/1763956#M216403</link>
      <description>&lt;P&gt;Hi team,&lt;/P&gt;&lt;P&gt;I am working on imx8qxp-mek board and trying to implement the secure boot in that BSP and currently we are using the NXP&amp;nbsp;&lt;SPAN&gt;LF6.1.36_2.1.0 release.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;I am using yocto build environment and using the imx-code-signing-tool package for it.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;A href="https://packages.debian.org/bookworm/arm64/imx-code-signing-tool/download" target="_blank"&gt;https://packages.debian.org/bookworm/arm64/imx-code-signing-tool/download&lt;/A&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;This package provides the cst binary and srktool but on running the&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;PRE&gt;./ahab_pki_tree.sh &lt;/PRE&gt;&lt;P&gt;Its still expecting the all required directory/filles as ca, openssl.conf and others.&lt;/P&gt;&lt;P&gt;its unable to create the certificates and keys there. If we just copy the cst.tgz and just replace the x86 cst binary with arm64 binary there we are getting the segmentation fault.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Please suggest on this issue, how to use this cst binary on imx8qxp-mek&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Rk&lt;/P&gt;</description>
      <pubDate>Mon, 27 Nov 2023 09:42:30 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/imx8qxp-mek-secure-boot-arm64-binary/m-p/1763956#M216403</guid>
      <dc:creator>rakesh3</dc:creator>
      <dc:date>2023-11-27T09:42:30Z</dc:date>
    </item>
    <item>
      <title>Re: imx8qxp-mek secure boot arm64 binary</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/imx8qxp-mek-secure-boot-arm64-binary/m-p/1764924#M216468</link>
      <description>&lt;P&gt;&lt;SPAN&gt;Debian currently does not support this, but it may be supported in the future.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Regards&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Harvey&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 28 Nov 2023 12:47:48 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/imx8qxp-mek-secure-boot-arm64-binary/m-p/1764924#M216468</guid>
      <dc:creator>Harvey021</dc:creator>
      <dc:date>2023-11-28T12:47:48Z</dc:date>
    </item>
  </channel>
</rss>

