<?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: Dose CSEc use quick write mode to update CSEc keys? in S32K</title>
    <link>https://community.nxp.com/t5/S32K/Dose-CSEc-use-quick-write-mode-to-update-CSEc-keys/m-p/1585893#M20147</link>
    <description>&lt;P&gt;Hi &lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/195334"&gt;@yaojianhang&lt;/a&gt; ,&lt;/P&gt;
&lt;P&gt;we do not provide more details about the implementation. Mentioned comment about interruption of s CSEc key update is still valid. There's only one requirement mentioned in the reference manual (at CMD_LOAD_KEY command):&lt;/P&gt;
&lt;P&gt;"Once a quick write is started, user must finish the entire&lt;BR /&gt;quick write activity prior to starting a LOAD_KEY&lt;BR /&gt;command."&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;Lukas&lt;/P&gt;</description>
    <pubDate>Fri, 20 Jan 2023 07:51:25 GMT</pubDate>
    <dc:creator>lukaszadrapa</dc:creator>
    <dc:date>2023-01-20T07:51:25Z</dc:date>
    <item>
      <title>Dose CSEc use quick write mode to update CSEc keys?</title>
      <link>https://community.nxp.com/t5/S32K/Dose-CSEc-use-quick-write-mode-to-update-CSEc-keys/m-p/1582776#M20017</link>
      <description>&lt;P&gt;HI,&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/37795"&gt;@lukaszadrapa&lt;/a&gt;&lt;/P&gt;&lt;P&gt;In S32K1xx reference manual CSEc chapter, it says interrupting a CSEc key update operation(due to power loss,reset....) whill leave the contents in an indeterminate state.&lt;/P&gt;&lt;P&gt;It seems that if CSEc update keys in quick write mode will solve the above problem, I am interested in S32K144, when update csec keys(located in EEPROM), how it actually works? write eeprom in quick write mode or normal write mode?&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;yaojianhang&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sun, 15 Jan 2023 11:14:36 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/Dose-CSEc-use-quick-write-mode-to-update-CSEc-keys/m-p/1582776#M20017</guid>
      <dc:creator>yaojianhang</dc:creator>
      <dc:date>2023-01-15T11:14:36Z</dc:date>
    </item>
    <item>
      <title>Re: Dose CSEc use quick write mode to update CSEc keys?</title>
      <link>https://community.nxp.com/t5/S32K/Dose-CSEc-use-quick-write-mode-to-update-CSEc-keys/m-p/1585893#M20147</link>
      <description>&lt;P&gt;Hi &lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/195334"&gt;@yaojianhang&lt;/a&gt; ,&lt;/P&gt;
&lt;P&gt;we do not provide more details about the implementation. Mentioned comment about interruption of s CSEc key update is still valid. There's only one requirement mentioned in the reference manual (at CMD_LOAD_KEY command):&lt;/P&gt;
&lt;P&gt;"Once a quick write is started, user must finish the entire&lt;BR /&gt;quick write activity prior to starting a LOAD_KEY&lt;BR /&gt;command."&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;Lukas&lt;/P&gt;</description>
      <pubDate>Fri, 20 Jan 2023 07:51:25 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/Dose-CSEc-use-quick-write-mode-to-update-CSEc-keys/m-p/1585893#M20147</guid>
      <dc:creator>lukaszadrapa</dc:creator>
      <dc:date>2023-01-20T07:51:25Z</dc:date>
    </item>
    <item>
      <title>Re: Dose CSEc use quick write mode to update CSEc keys?</title>
      <link>https://community.nxp.com/t5/S32K/Dose-CSEc-use-quick-write-mode-to-update-CSEc-keys/m-p/1586360#M20169</link>
      <description>&lt;P&gt;thanks for your reply.&lt;/P&gt;</description>
      <pubDate>Sun, 22 Jan 2023 06:58:06 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/Dose-CSEc-use-quick-write-mode-to-update-CSEc-keys/m-p/1586360#M20169</guid>
      <dc:creator>yaojianhang</dc:creator>
      <dc:date>2023-01-22T06:58:06Z</dc:date>
    </item>
  </channel>
</rss>

