<?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 Layerscape secure boot with Yocto for 1028A family in Other NXP Products</title>
    <link>https://community.nxp.com/t5/Other-NXP-Products/Layerscape-secure-boot-with-Yocto-for-1028A-family/m-p/1654547#M17822</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I am currently trying to get acquainted with the secure boot implementation on Layerscape processors. I have been reading a lot in the &lt;A href="https://docs.nxp.com/bundle/GUID-3FFCCD77-5220-414D-8664-09E6FB1B02C6/page/GUID-C920A8C4-3D1E-448F-9D1C-016B27FCB767.html" target="_self"&gt;documentation&lt;/A&gt; in the last days, but it is still not clear to me how everything works.&lt;/P&gt;&lt;P&gt;From what I understand these are the boot stages:&lt;/P&gt;&lt;P&gt;BL1 &amp;nbsp; : BootROM code&lt;BR /&gt;BL2 &amp;nbsp; : Pre-Bootloader&lt;BR /&gt;BL31 : EL3 runtime firmware&lt;BR /&gt;BL32 : OP-TEE (optional)&lt;BR /&gt;BL33 : U-Boot&lt;/P&gt;&lt;P&gt;&lt;A href="https://docs.nxp.com/bundle/GUID-3FFCCD77-5220-414D-8664-09E6FB1B02C6/page/GUID-819A6D70-AAED-4B6C-BDA6-7A1B98B77784.html" target="_self"&gt;All stages seem to be verified with a CSF header&lt;/A&gt; that contains the commands, pointers and checksums of the images to be verified. Is the same CSF header used for all stages?&lt;BR /&gt;&lt;BR /&gt;&lt;A href="https://github.com/Freescale/meta-freescale/blob/master/recipes-bsp/atf/qoriq-atf_2.6.bb" target="_self"&gt;The Bitbake recipe here&lt;/A&gt; seems to take care of the signing and fusing process. I don't fully understand all parts of the recipe, but is it sufficient to provide your own SRK files to automatically sign the images and build the fuse provisioning image?&lt;/P&gt;</description>
    <pubDate>Mon, 22 May 2023 07:53:01 GMT</pubDate>
    <dc:creator>jclsn</dc:creator>
    <dc:date>2023-05-22T07:53:01Z</dc:date>
    <item>
      <title>Layerscape secure boot with Yocto for 1028A family</title>
      <link>https://community.nxp.com/t5/Other-NXP-Products/Layerscape-secure-boot-with-Yocto-for-1028A-family/m-p/1654547#M17822</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I am currently trying to get acquainted with the secure boot implementation on Layerscape processors. I have been reading a lot in the &lt;A href="https://docs.nxp.com/bundle/GUID-3FFCCD77-5220-414D-8664-09E6FB1B02C6/page/GUID-C920A8C4-3D1E-448F-9D1C-016B27FCB767.html" target="_self"&gt;documentation&lt;/A&gt; in the last days, but it is still not clear to me how everything works.&lt;/P&gt;&lt;P&gt;From what I understand these are the boot stages:&lt;/P&gt;&lt;P&gt;BL1 &amp;nbsp; : BootROM code&lt;BR /&gt;BL2 &amp;nbsp; : Pre-Bootloader&lt;BR /&gt;BL31 : EL3 runtime firmware&lt;BR /&gt;BL32 : OP-TEE (optional)&lt;BR /&gt;BL33 : U-Boot&lt;/P&gt;&lt;P&gt;&lt;A href="https://docs.nxp.com/bundle/GUID-3FFCCD77-5220-414D-8664-09E6FB1B02C6/page/GUID-819A6D70-AAED-4B6C-BDA6-7A1B98B77784.html" target="_self"&gt;All stages seem to be verified with a CSF header&lt;/A&gt; that contains the commands, pointers and checksums of the images to be verified. Is the same CSF header used for all stages?&lt;BR /&gt;&lt;BR /&gt;&lt;A href="https://github.com/Freescale/meta-freescale/blob/master/recipes-bsp/atf/qoriq-atf_2.6.bb" target="_self"&gt;The Bitbake recipe here&lt;/A&gt; seems to take care of the signing and fusing process. I don't fully understand all parts of the recipe, but is it sufficient to provide your own SRK files to automatically sign the images and build the fuse provisioning image?&lt;/P&gt;</description>
      <pubDate>Mon, 22 May 2023 07:53:01 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Other-NXP-Products/Layerscape-secure-boot-with-Yocto-for-1028A-family/m-p/1654547#M17822</guid>
      <dc:creator>jclsn</dc:creator>
      <dc:date>2023-05-22T07:53:01Z</dc:date>
    </item>
    <item>
      <title>Re: Layerscape secure boot with Yocto for 1028A family</title>
      <link>https://community.nxp.com/t5/Other-NXP-Products/Layerscape-secure-boot-with-Yocto-for-1028A-family/m-p/1658261#M17898</link>
      <description>So I could progress a bit. Seems like you need to copy the srk.pri and srk.pub into the work directory of the qoriq-atf recipe to sign the images.&lt;BR /&gt;&lt;BR /&gt;Only thing left is the fuse_fip.bin. Seems like you need to provide the input_fuse_file and add the OTMPK and SRKH. I am still not quite sure if I am doing this right. The gen_otpmk_drbg command can generate you the OTPMK and the SRKH can be generated by the uni_pbi command provided the input_pbi_flexspi_nor_secure file. In the documentation it says that the SRKH is merely a SHA-256 sum calculated over the srk.pub, but it I run&lt;BR /&gt;&lt;BR /&gt;$ sha256sum srk.pub&lt;BR /&gt;&lt;BR /&gt;I get a different hash than with the uni_pbi command. Can you please clarify why that happens?</description>
      <pubDate>Fri, 26 May 2023 09:12:42 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Other-NXP-Products/Layerscape-secure-boot-with-Yocto-for-1028A-family/m-p/1658261#M17898</guid>
      <dc:creator>jclsn</dc:creator>
      <dc:date>2023-05-26T09:12:42Z</dc:date>
    </item>
  </channel>
</rss>

