<?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: S32K146_Csec in S32K</title>
    <link>https://community.nxp.com/t5/S32K/S32K146-Csec/m-p/1693830#M25493</link>
    <description>&lt;P&gt;Hi &lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/204726"&gt;@Kris_chao&lt;/a&gt; &lt;BR /&gt;to destroy the partition (to reset the device back to factory state), it is necessary to run CMD_DBG_CHAL and CMD_DBG_AUTH commands with knowledge of MASTER_ECU_KEY. &lt;BR /&gt;If you use software from AN5401, you can run 5_Resetting_flash_to_the_factory_state project. If you modified default MASTER_ECU_KEY, you need to update the key in DBG_AUTH function in CSEc_functions.c file.&lt;/P&gt;
&lt;P&gt;If you use SDK code, you can run this project:&lt;BR /&gt;c:\NXP\S32DS.3.4\S32DS\software\S32SDK_S32K1XX_RTM_4.0.3\examples\S32K146\driver_examples\system\csec_keyconfig\&lt;BR /&gt;Just change this definition from:&lt;BR /&gt;#define ERASE_ALL_KEYS 0&lt;BR /&gt;to &lt;BR /&gt;#define ERASE_ALL_KEYS 1&lt;BR /&gt;And again, if you changed the MASTER_ECU_KEY, make sure it is updated in file csec_utils.c accordingly (g_authIdKey).&lt;/P&gt;
&lt;P&gt;And if you want to update BOOT_MAC without destroying the partition, it is possible to - you can update it using standard key update protocol. It's described in section "4.4.4.2 Scenario 2: One or more keys is write protected and all user&lt;BR /&gt;keys cannot be erased. (or not all user keys are known)" in AN5401.&lt;BR /&gt;Regards,&lt;BR /&gt;Lukas&lt;/P&gt;</description>
    <pubDate>Thu, 27 Jul 2023 06:03:30 GMT</pubDate>
    <dc:creator>lukaszadrapa</dc:creator>
    <dc:date>2023-07-27T06:03:30Z</dc:date>
    <item>
      <title>S32K146_Csec</title>
      <link>https://community.nxp.com/t5/S32K/S32K146-Csec/m-p/1692966#M25454</link>
      <description>&lt;P&gt;各位大佬，想问一下这个S32K的Csec模块，我在反刷了Boot后需要更新BOOT_MAC值，但又不能重置Flexram和Flexnvm区域，有什么好的办法？&lt;/P&gt;</description>
      <pubDate>Wed, 26 Jul 2023 09:56:39 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/S32K146-Csec/m-p/1692966#M25454</guid>
      <dc:creator>Kris_chao</dc:creator>
      <dc:date>2023-07-26T09:56:39Z</dc:date>
    </item>
    <item>
      <title>Re: S32K146_Csec</title>
      <link>https://community.nxp.com/t5/S32K/S32K146-Csec/m-p/1693830#M25493</link>
      <description>&lt;P&gt;Hi &lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/204726"&gt;@Kris_chao&lt;/a&gt; &lt;BR /&gt;to destroy the partition (to reset the device back to factory state), it is necessary to run CMD_DBG_CHAL and CMD_DBG_AUTH commands with knowledge of MASTER_ECU_KEY. &lt;BR /&gt;If you use software from AN5401, you can run 5_Resetting_flash_to_the_factory_state project. If you modified default MASTER_ECU_KEY, you need to update the key in DBG_AUTH function in CSEc_functions.c file.&lt;/P&gt;
&lt;P&gt;If you use SDK code, you can run this project:&lt;BR /&gt;c:\NXP\S32DS.3.4\S32DS\software\S32SDK_S32K1XX_RTM_4.0.3\examples\S32K146\driver_examples\system\csec_keyconfig\&lt;BR /&gt;Just change this definition from:&lt;BR /&gt;#define ERASE_ALL_KEYS 0&lt;BR /&gt;to &lt;BR /&gt;#define ERASE_ALL_KEYS 1&lt;BR /&gt;And again, if you changed the MASTER_ECU_KEY, make sure it is updated in file csec_utils.c accordingly (g_authIdKey).&lt;/P&gt;
&lt;P&gt;And if you want to update BOOT_MAC without destroying the partition, it is possible to - you can update it using standard key update protocol. It's described in section "4.4.4.2 Scenario 2: One or more keys is write protected and all user&lt;BR /&gt;keys cannot be erased. (or not all user keys are known)" in AN5401.&lt;BR /&gt;Regards,&lt;BR /&gt;Lukas&lt;/P&gt;</description>
      <pubDate>Thu, 27 Jul 2023 06:03:30 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/S32K146-Csec/m-p/1693830#M25493</guid>
      <dc:creator>lukaszadrapa</dc:creator>
      <dc:date>2023-07-27T06:03:30Z</dc:date>
    </item>
  </channel>
</rss>

