<?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>S12 / MagniV MicrocontrollersのトピックSoftware security issue</title>
    <link>https://community.nxp.com/t5/S12-MagniV-Microcontrollers/Software-security-issue/m-p/1974881#M20190</link>
    <description>&lt;P&gt;Dear&amp;nbsp; team:&lt;/P&gt;&lt;P&gt;we used s12zvm31 mcu to develop products&lt;/P&gt;&lt;P&gt;Could you tell me&amp;nbsp;&amp;nbsp;how to set up software to prevent mass production software from being cracked. thanks.&lt;/P&gt;</description>
    <pubDate>Wed, 16 Oct 2024 06:54:19 GMT</pubDate>
    <dc:creator>ltxdl</dc:creator>
    <dc:date>2024-10-16T06:54:19Z</dc:date>
    <item>
      <title>Software security issue</title>
      <link>https://community.nxp.com/t5/S12-MagniV-Microcontrollers/Software-security-issue/m-p/1974881#M20190</link>
      <description>&lt;P&gt;Dear&amp;nbsp; team:&lt;/P&gt;&lt;P&gt;we used s12zvm31 mcu to develop products&lt;/P&gt;&lt;P&gt;Could you tell me&amp;nbsp;&amp;nbsp;how to set up software to prevent mass production software from being cracked. thanks.&lt;/P&gt;</description>
      <pubDate>Wed, 16 Oct 2024 06:54:19 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S12-MagniV-Microcontrollers/Software-security-issue/m-p/1974881#M20190</guid>
      <dc:creator>ltxdl</dc:creator>
      <dc:date>2024-10-16T06:54:19Z</dc:date>
    </item>
    <item>
      <title>Re: Software security issue</title>
      <link>https://community.nxp.com/t5/S12-MagniV-Microcontrollers/Software-security-issue/m-p/1976114#M20198</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;if you do not change anything in the flash security byte (can be checked in s19 record) then the device is secured after loading by default.&lt;/P&gt;
&lt;P&gt;The BDM always mass erase/unsecures it for debugging before programming. If you only program it (debugger does not prepare device for debugging) with no access to the security byte then it will be secured and not debeggable.&lt;/P&gt;
&lt;P&gt;The example of security with temporary unsecuring by special 64bit code received by application can be seen here&lt;/P&gt;
&lt;P&gt;&lt;A href="https://community.nxp.com/t5/S12-MagniV-Microcontrollers/SW-example-of-Security-feature-with-Backdoor-Access-Key-option/ta-p/1104462" target="_blank"&gt;https://community.nxp.com/t5/S12-MagniV-Microcontrollers/SW-example-of-Security-feature-with-Backdoor-Access-Key-option/ta-p/1104462&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;The code for temporary unsecure (up to next reset) can be received by some peripheral or it can be launched by some specific event/condition with backdoor key stored in application code as presented in the example.&lt;/P&gt;
&lt;P&gt;It is up to you whether you want to use backdoor key. If not use the device can not be unsecured only BDM mass errase command is available.&lt;/P&gt;
&lt;P&gt;Best regards,&lt;/P&gt;
&lt;P&gt;Ladislav&lt;/P&gt;
&lt;P&gt;&lt;A href="https://community.nxp.com/t5/S12-MagniV-Microcontrollers/S12Z-unsecure/m-p/1303088" target="_blank"&gt;https://community.nxp.com/t5/S12-MagniV-Microcontrollers/S12Z-unsecure/m-p/1303088&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 17 Oct 2024 13:25:29 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S12-MagniV-Microcontrollers/Software-security-issue/m-p/1976114#M20198</guid>
      <dc:creator>lama</dc:creator>
      <dc:date>2024-10-17T13:25:29Z</dc:date>
    </item>
    <item>
      <title>Re: Software security issue</title>
      <link>https://community.nxp.com/t5/S12-MagniV-Microcontrollers/Software-security-issue/m-p/1995791#M20229</link>
      <description>Hello Team,&lt;BR /&gt;We are using the same example code to unsecure the S12Z device ( we receive the stimulus to unlock via SPI ) and we see that the MCU is not getting unsecured. We could transmit the FSEC register value over the SPI we still read as 01 in boolean meaning secured and not 10 in boolean meaning unsecured, any attach option via CW and Cyclone Pro debugger also show that the MCU is still secured. Please Could you provide your feedback here. Timeline is critical for our project as we have the production Dates coming near, Quick support would be appreicated.</description>
      <pubDate>Sun, 17 Nov 2024 06:56:45 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S12-MagniV-Microcontrollers/Software-security-issue/m-p/1995791#M20229</guid>
      <dc:creator>ChristopherLenordJ</dc:creator>
      <dc:date>2024-11-17T06:56:45Z</dc:date>
    </item>
  </channel>
</rss>

