<?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 strict mode code size update in S32K</title>
    <link>https://community.nxp.com/t5/S32K/S32K146-CSEc-strict-mode-code-size-update/m-p/1953084#M40870</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;&amp;nbsp;,&lt;/P&gt;&lt;P&gt;Thank you very much for your support, let's see what they say.&lt;/P&gt;&lt;P&gt;Best regards,&lt;/P&gt;&lt;P&gt;Carlos&lt;/P&gt;</description>
    <pubDate>Thu, 12 Sep 2024 06:12:51 GMT</pubDate>
    <dc:creator>sinixtek</dc:creator>
    <dc:date>2024-09-12T06:12:51Z</dc:date>
    <item>
      <title>S32K146 CSEc strict mode code size update</title>
      <link>https://community.nxp.com/t5/S32K/S32K146-CSEc-strict-mode-code-size-update/m-p/1949764#M40686</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;We are developing a solution in which we need to enable CSEc strict mode.&lt;/P&gt;&lt;P&gt;When we do, by using the boot flavor '00' in the command CMD_BOOT_DEFINE, everything works fine.&lt;/P&gt;&lt;P&gt;However, after rebooting, if we update our boot loader and we try to define a new BOOT_SIZE, the command fails with code 0x800.&lt;/P&gt;&lt;P&gt;Even if we try to update with the same BOOT_SIZE, the command fails, no matter the Boot Flavor we use in the command. If we ignore the error and reboot, the part is bricked (even using the same BOOT_SIZE and updating the MAC appropriately).&lt;/P&gt;&lt;P&gt;The same process works without issue if the Sequential Boot Method is selected. The documentation states that Strict mode is OTP, but that BOOT_SIZE can be changed.&lt;/P&gt;&lt;P&gt;How can we update BOOT_SIZE in Strict mode?&lt;/P&gt;&lt;P&gt;Thank you very much!&lt;/P&gt;</description>
      <pubDate>Mon, 09 Sep 2024 06:19:08 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/S32K146-CSEc-strict-mode-code-size-update/m-p/1949764#M40686</guid>
      <dc:creator>sinixtek</dc:creator>
      <dc:date>2024-09-09T06:19:08Z</dc:date>
    </item>
    <item>
      <title>Re: S32K146 CSEc strict mode code size update</title>
      <link>https://community.nxp.com/t5/S32K/S32K146-CSEc-strict-mode-code-size-update/m-p/1952048#M40833</link>
      <description>&lt;P&gt;Hi &lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/181807"&gt;@sinixtek&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;That's a good question, I have never tried this use-case. It looks like you are the first one who is trying to change the BOOT_SIZE in strict boot mode. Please give me more time to clarify this. I will probably need to discuss this with another team, so it may take some time. At a glance, my guess is that it's not supported even if the documentation says something different. But let's wait for the result.&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;Lukas&lt;/P&gt;</description>
      <pubDate>Wed, 11 Sep 2024 11:38:13 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/S32K146-CSEc-strict-mode-code-size-update/m-p/1952048#M40833</guid>
      <dc:creator>lukaszadrapa</dc:creator>
      <dc:date>2024-09-11T11:38:13Z</dc:date>
    </item>
    <item>
      <title>Re: S32K146 CSEc strict mode code size update</title>
      <link>https://community.nxp.com/t5/S32K/S32K146-CSEc-strict-mode-code-size-update/m-p/1953084#M40870</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;&amp;nbsp;,&lt;/P&gt;&lt;P&gt;Thank you very much for your support, let's see what they say.&lt;/P&gt;&lt;P&gt;Best regards,&lt;/P&gt;&lt;P&gt;Carlos&lt;/P&gt;</description>
      <pubDate>Thu, 12 Sep 2024 06:12:51 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/S32K146-CSEc-strict-mode-code-size-update/m-p/1953084#M40870</guid>
      <dc:creator>sinixtek</dc:creator>
      <dc:date>2024-09-12T06:12:51Z</dc:date>
    </item>
    <item>
      <title>Re: S32K146 CSEc strict mode code size update</title>
      <link>https://community.nxp.com/t5/S32K/S32K146-CSEc-strict-mode-code-size-update/m-p/1956524#M41057</link>
      <description>&lt;P&gt;Hi &lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/181807"&gt;@sinixtek&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;the result is that the SIZE cannot be updated. The sentence in the manual is confusing, I asked to update it.&lt;/P&gt;
&lt;P&gt;Thanks for pointing this out.&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;Lukas&lt;/P&gt;</description>
      <pubDate>Wed, 18 Sep 2024 09:46:29 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/S32K146-CSEc-strict-mode-code-size-update/m-p/1956524#M41057</guid>
      <dc:creator>lukaszadrapa</dc:creator>
      <dc:date>2024-09-18T09:46:29Z</dc:date>
    </item>
    <item>
      <title>Re: S32K146 CSEc strict mode code size update</title>
      <link>https://community.nxp.com/t5/S32K/S32K146-CSEc-strict-mode-code-size-update/m-p/1957353#M41113</link>
      <description>&lt;P&gt;Thank you very much for clarifying this.&lt;/P&gt;&lt;P&gt;Best regards,&lt;/P&gt;&lt;P&gt;Carlos&lt;/P&gt;</description>
      <pubDate>Thu, 19 Sep 2024 07:35:56 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/S32K146-CSEc-strict-mode-code-size-update/m-p/1957353#M41113</guid>
      <dc:creator>sinixtek</dc:creator>
      <dc:date>2024-09-19T07:35:56Z</dc:date>
    </item>
  </channel>
</rss>

