<?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: S32K14x JTAG lock in S32K</title>
    <link>https://community.nxp.com/t5/S32K/S32K14x-JTAG-lock/m-p/1597337#M20580</link>
    <description>Do you mean that j-flash burning program will cause a reset? In addition, j-flash read back to flash is also failed. So I wanted to know exactly what the unlocked swd mode feature would do.</description>
    <pubDate>Fri, 10 Feb 2023 12:56:25 GMT</pubDate>
    <dc:creator>zhou_gaga</dc:creator>
    <dc:date>2023-02-10T12:56:25Z</dc:date>
    <item>
      <title>S32K14x JTAG lock</title>
      <link>https://community.nxp.com/t5/S32K/S32K14x-JTAG-lock/m-p/1597091#M20561</link>
      <description>&lt;P&gt;&lt;SPAN class=""&gt;I use backdoor_key_verify to implement JTAG unlock, and CAN send FTFC-&amp;amp;gt before and after using backdoor_key_verify;&lt;/SPAN&gt;&lt;SPAN class=""&gt; The FSEC state, we see from the beginning FSEC[SEC]=11b changes to FSEC[SEC]=10b, so the jtag unlocked, but I still won't get through the J-FLASH burning program.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 10 Feb 2023 07:10:31 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/S32K14x-JTAG-lock/m-p/1597091#M20561</guid>
      <dc:creator>zhou_gaga</dc:creator>
      <dc:date>2023-02-10T07:10:31Z</dc:date>
    </item>
    <item>
      <title>Re: S32K14x JTAG lock</title>
      <link>https://community.nxp.com/t5/S32K/S32K14x-JTAG-lock/m-p/1597292#M20578</link>
      <description>&lt;P&gt;Hello &lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/212187"&gt;@zhou_gaga&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;The MCU stays unloked as long as the MCU is not reset.&lt;/P&gt;
&lt;P&gt;After any reset, the MCU is locked again.&lt;/P&gt;
&lt;P&gt;So, the programmer must not reset the MCU.&lt;/P&gt;
&lt;P&gt;Please contact SEGGER support if you want to reprogram the MCU using J-Flash.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thank you,&lt;/P&gt;
&lt;P&gt;BR, Daniel&lt;/P&gt;</description>
      <pubDate>Fri, 10 Feb 2023 11:40:46 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/S32K14x-JTAG-lock/m-p/1597292#M20578</guid>
      <dc:creator>danielmartynek</dc:creator>
      <dc:date>2023-02-10T11:40:46Z</dc:date>
    </item>
    <item>
      <title>Re: S32K14x JTAG lock</title>
      <link>https://community.nxp.com/t5/S32K/S32K14x-JTAG-lock/m-p/1597337#M20580</link>
      <description>Do you mean that j-flash burning program will cause a reset? In addition, j-flash read back to flash is also failed. So I wanted to know exactly what the unlocked swd mode feature would do.</description>
      <pubDate>Fri, 10 Feb 2023 12:56:25 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/S32K14x-JTAG-lock/m-p/1597337#M20580</guid>
      <dc:creator>zhou_gaga</dc:creator>
      <dc:date>2023-02-10T12:56:25Z</dc:date>
    </item>
    <item>
      <title>Re: S32K14x JTAG lock</title>
      <link>https://community.nxp.com/t5/S32K/S32K14x-JTAG-lock/m-p/1597399#M20587</link>
      <description>&lt;P&gt;For example, the PEMicro plugin in the S32DS IDE has this feature that allow connecting the programmer without reset.&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="danielmartynek_0-1676038785167.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/210501i852077B7BA1EAE67/image-size/medium?v=v2&amp;amp;px=400" role="button" title="danielmartynek_0-1676038785167.png" alt="danielmartynek_0-1676038785167.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;This way, we can attach the debugger while the MCU is unlocked and running.&lt;/P&gt;
&lt;P&gt;For more information about the J-Flash flashing algorithm, please contact SEGGER.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thank you,&lt;/P&gt;
&lt;P&gt;BR, Daniel&lt;/P&gt;</description>
      <pubDate>Fri, 10 Feb 2023 14:21:56 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/S32K14x-JTAG-lock/m-p/1597399#M20587</guid>
      <dc:creator>danielmartynek</dc:creator>
      <dc:date>2023-02-10T14:21:56Z</dc:date>
    </item>
    <item>
      <title>Re: S32K14x JTAG lock</title>
      <link>https://community.nxp.com/t5/S32K/S32K14x-JTAG-lock/m-p/1597437#M20591</link>
      <description>&lt;P&gt;Besides, can I burn a new program after jtag unlocked? If so, how to operate it?&lt;/P&gt;</description>
      <pubDate>Fri, 10 Feb 2023 15:26:36 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/S32K14x-JTAG-lock/m-p/1597437#M20591</guid>
      <dc:creator>zhou_gaga</dc:creator>
      <dc:date>2023-02-10T15:26:36Z</dc:date>
    </item>
    <item>
      <title>Re: S32K14x JTAG lock</title>
      <link>https://community.nxp.com/t5/S32K/S32K14x-JTAG-lock/m-p/1597780#M20615</link>
      <description>I tried the method you said, but the PE displayed "Warning: Unable to go to background. Core is running", but the CAN message showed FSEC[SEC]=10b (unsecured).</description>
      <pubDate>Mon, 13 Feb 2023 02:24:53 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/S32K14x-JTAG-lock/m-p/1597780#M20615</guid>
      <dc:creator>zhou_gaga</dc:creator>
      <dc:date>2023-02-13T02:24:53Z</dc:date>
    </item>
    <item>
      <title>Re: S32K14x JTAG lock</title>
      <link>https://community.nxp.com/t5/S32K/S32K14x-JTAG-lock/m-p/1598756#M20659</link>
      <description>&lt;P&gt;Hello &lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/212187"&gt;@zhou_gaga&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;You are supposed to get a warning, the core is running.&lt;/P&gt;
&lt;P&gt;The debugger is attached to a running target.&lt;/P&gt;
&lt;P&gt;Can you halt the execution?&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="danielmartynek_0-1676365764660.png" style="width: 647px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/210828i9E0730D0DA808EA9/image-dimensions/647x280?v=v2" width="647" height="280" role="button" title="danielmartynek_0-1676365764660.png" alt="danielmartynek_0-1676365764660.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;Daniel&lt;/P&gt;</description>
      <pubDate>Tue, 14 Feb 2023 09:10:09 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/S32K14x-JTAG-lock/m-p/1598756#M20659</guid>
      <dc:creator>danielmartynek</dc:creator>
      <dc:date>2023-02-14T09:10:09Z</dc:date>
    </item>
    <item>
      <title>Re: S32K14x JTAG lock</title>
      <link>https://community.nxp.com/t5/S32K/S32K14x-JTAG-lock/m-p/1599360#M20687</link>
      <description>Suddenly it can read. But I still have a question, if PE is configured as "Attach to Running Target", then will MCU load the previous program or the program of the current project? Also, if I unlock through backdoors, how do I burn new programs?</description>
      <pubDate>Wed, 15 Feb 2023 07:07:47 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/S32K14x-JTAG-lock/m-p/1599360#M20687</guid>
      <dc:creator>zhou_gaga</dc:creator>
      <dc:date>2023-02-15T07:07:47Z</dc:date>
    </item>
    <item>
      <title>Re: S32K14x JTAG lock</title>
      <link>https://community.nxp.com/t5/S32K/S32K14x-JTAG-lock/m-p/1599571#M20696</link>
      <description>&lt;P&gt;Hello &lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/212187"&gt;@zhou_gaga&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;In the attach debug session, the MCU is not being programmed, it is just attached to the MCU while the MCU is running the previously loaded project.&lt;/P&gt;
&lt;P&gt;I would recommend contacting PEMicro support and ask for an algorithm the does not reset the MCU before the flashing.&lt;/P&gt;
&lt;P&gt;You could also you J-link commander:&lt;/P&gt;
&lt;P&gt;Once the MCU is unlocked, a special J-Link script is necessary, which can be found here: &lt;A href="https://wiki.segger.com/S32Kxxx#Attach_to_debug_session" target="_blank" rel="noopener"&gt;https://wiki.segger.com/S32Kxxx#Attach_to_debug_session&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;J-Link commander need to be called in the following way:&lt;/P&gt;
&lt;P&gt;C:\Programm\SEGGER\JLink\JLink.exe -JLinkScriptFile NXP_Kinetis_S32_Attach.JLinkScript&lt;/P&gt;
&lt;P&gt;Then, the MCU is not reseted and access to all memory and registers is possible.&lt;/P&gt;
&lt;P&gt;You can try to load the project via the commander.&lt;/P&gt;
&lt;P&gt;Or please contact SEGGER support.&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;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 15 Feb 2023 11:51:13 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/S32K14x-JTAG-lock/m-p/1599571#M20696</guid>
      <dc:creator>danielmartynek</dc:creator>
      <dc:date>2023-02-15T11:51:13Z</dc:date>
    </item>
  </channel>
</rss>

