<?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: How to unsecure the mcu using backdoor key access in S32K</title>
    <link>https://community.nxp.com/t5/S32K/How-to-unsecure-the-mcu-using-backdoor-key-access/m-p/622183#M217</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;When the MCU is secure, the debugger can’t read registers, it has no access to the MCU except for mass erase which will unlock the MCU. The MCU can be unsecured by the code itself using Verify Backdoor Access Key command.&lt;/P&gt;&lt;P&gt;Please refer to the example code. The MCU is secured in the start-up code (startup_S32K144.S), see Flash Configuration, backdoor comparison key: 0xAAAAAAAAAAAAAAAA.&lt;/P&gt;&lt;P&gt;Power-on reset is needed to run the MCU stand alone. Red LED on the EVB indicates the MCU is secure.&lt;/P&gt;&lt;P&gt;Verify backdoor key command, which will unlock the MCU and which is executed from RAM, is delayed with a delay loop. After that the MCU will be unsecured and the LED will turn BLUE.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Daniel&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 20 Apr 2017 21:10:01 GMT</pubDate>
    <dc:creator>danielmartynek</dc:creator>
    <dc:date>2017-04-20T21:10:01Z</dc:date>
    <item>
      <title>How to unsecure the mcu using backdoor key access</title>
      <link>https://community.nxp.com/t5/S32K/How-to-unsecure-the-mcu-using-backdoor-key-access/m-p/622182#M216</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;When the mcu was secured, then how to unsecure the mcu using backdoor key access？How to know the contents of the 8-bytes backdoor key value stored in the Flash?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 19 Apr 2017 12:37:26 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/How-to-unsecure-the-mcu-using-backdoor-key-access/m-p/622182#M216</guid>
      <dc:creator>jimfung</dc:creator>
      <dc:date>2017-04-19T12:37:26Z</dc:date>
    </item>
    <item>
      <title>Re: How to unsecure the mcu using backdoor key access</title>
      <link>https://community.nxp.com/t5/S32K/How-to-unsecure-the-mcu-using-backdoor-key-access/m-p/622183#M217</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;When the MCU is secure, the debugger can’t read registers, it has no access to the MCU except for mass erase which will unlock the MCU. The MCU can be unsecured by the code itself using Verify Backdoor Access Key command.&lt;/P&gt;&lt;P&gt;Please refer to the example code. The MCU is secured in the start-up code (startup_S32K144.S), see Flash Configuration, backdoor comparison key: 0xAAAAAAAAAAAAAAAA.&lt;/P&gt;&lt;P&gt;Power-on reset is needed to run the MCU stand alone. Red LED on the EVB indicates the MCU is secure.&lt;/P&gt;&lt;P&gt;Verify backdoor key command, which will unlock the MCU and which is executed from RAM, is delayed with a delay loop. After that the MCU will be unsecured and the LED will turn BLUE.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Daniel&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 20 Apr 2017 21:10:01 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/How-to-unsecure-the-mcu-using-backdoor-key-access/m-p/622183#M217</guid>
      <dc:creator>danielmartynek</dc:creator>
      <dc:date>2017-04-20T21:10:01Z</dc:date>
    </item>
    <item>
      <title>Re: How to unsecure the mcu using backdoor key access</title>
      <link>https://community.nxp.com/t5/S32K/How-to-unsecure-the-mcu-using-backdoor-key-access/m-p/622184#M218</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Daniel,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for help!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards,&lt;/P&gt;&lt;P&gt;Jim&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 21 Apr 2017 01:04:06 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/How-to-unsecure-the-mcu-using-backdoor-key-access/m-p/622184#M218</guid>
      <dc:creator>jimfung</dc:creator>
      <dc:date>2017-04-21T01:04:06Z</dc:date>
    </item>
    <item>
      <title>Re: How to unsecure the mcu using backdoor key access</title>
      <link>https://community.nxp.com/t5/S32K/How-to-unsecure-the-mcu-using-backdoor-key-access/m-p/622185#M219</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Daniel,&lt;/P&gt;&lt;P&gt;I'm having the same issue. I imported your project and try to build it however&amp;nbsp; I get the following errors:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;./src/main.o: In function `main':&lt;/P&gt;&lt;P&gt;C:\ECLIPSE_WS\S32K144_backdoor_key_access_S32DS1.3\Debug_RAM/../src/main.c:166: undefined reference to `__MY_RAM_SIZE'&lt;/P&gt;&lt;P&gt;C:\ECLIPSE_WS\S32K144_backdoor_key_access_S32DS1.3\Debug_RAM/../src/main.c:166: undefined reference to `__MY_RAM_ADR'&lt;/P&gt;&lt;P&gt;C:\ECLIPSE_WS\S32K144_backdoor_key_access_S32DS1.3\Debug_RAM/../src/main.c:166: undefined reference to `__MY_RAM_ROM_ADR'&lt;/P&gt;&lt;P&gt;collect2.exe: error: ld returned 1 exit status&lt;/P&gt;&lt;P&gt;make: *** [S32K144_backdoor_key_access_S32DS1.3.elf] Error 1&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I thought may be they are in the linker file, but I just can't find them.&lt;/P&gt;&lt;P&gt;Any ideas?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Koorosh Hajiani&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 10 May 2017 15:57:26 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/How-to-unsecure-the-mcu-using-backdoor-key-access/m-p/622185#M219</guid>
      <dc:creator>hajianik</dc:creator>
      <dc:date>2017-05-10T15:57:26Z</dc:date>
    </item>
  </channel>
</rss>

