<?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 S32K3 secure boot in S32K</title>
    <link>https://community.nxp.com/t5/S32K/S32K3-secure-boot/m-p/1726179#M27229</link>
    <description>&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;The HSE firmware is ab _ swap.&amp;nbsp; If secure boot is to be done, do both block0 and block1 need a separate bootloader.&lt;/P&gt;</description>
    <pubDate>Wed, 20 Sep 2023 09:14:02 GMT</pubDate>
    <dc:creator>youxi</dc:creator>
    <dc:date>2023-09-20T09:14:02Z</dc:date>
    <item>
      <title>S32K3 secure boot</title>
      <link>https://community.nxp.com/t5/S32K/S32K3-secure-boot/m-p/1726179#M27229</link>
      <description>&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;The HSE firmware is ab _ swap.&amp;nbsp; If secure boot is to be done, do both block0 and block1 need a separate bootloader.&lt;/P&gt;</description>
      <pubDate>Wed, 20 Sep 2023 09:14:02 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/S32K3-secure-boot/m-p/1726179#M27229</guid>
      <dc:creator>youxi</dc:creator>
      <dc:date>2023-09-20T09:14:02Z</dc:date>
    </item>
    <item>
      <title>Re: S32K3 secure boot</title>
      <link>https://community.nxp.com/t5/S32K/S32K3-secure-boot/m-p/1727135#M27284</link>
      <description>&lt;P&gt;No, this solution do not use two bootloaders. Pointers between active and passive partitions are being changed.&lt;/P&gt;</description>
      <pubDate>Thu, 21 Sep 2023 12:09:06 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/S32K3-secure-boot/m-p/1727135#M27284</guid>
      <dc:creator>davidtosenovjan</dc:creator>
      <dc:date>2023-09-21T12:09:06Z</dc:date>
    </item>
  </channel>
</rss>

