<?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: Chip deadlock in S32K</title>
    <link>https://community.nxp.com/t5/S32K/Chip-deadlock/m-p/1668826#M23918</link>
    <description>&lt;P&gt;&lt;A href="mailto:Hi@zxc1" target="_blank"&gt;Hi@zxc1&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;If you only modified this part, you can try to disable security using Mass Erase.&lt;BR /&gt;（Remember, if you use the CESc module and allocate CSEc with key, please do not try to use Mass Erase to erase the chip directly）&lt;/P&gt;
&lt;P&gt;1.if you're using PE&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Senlent_0-1686712133758.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/227526iB9A0277E680F4608/image-size/medium?v=v2&amp;amp;px=400" role="button" title="Senlent_0-1686712133758.png" alt="Senlent_0-1686712133758.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;2.J-Link&lt;/P&gt;
&lt;P&gt;&lt;A href="https://community.nxp.com/t5/S32K/S32K148-Unsecurity/m-p/1182938?lightbox-message-images-1176957=128885iE01BFC9C805C3F38" target="_self"&gt;https://community.nxp.com/t5/S32K/S32K148-Unsecurity/m-p/1182938?lightbox-message-images-1176957=128885iE01BFC9C805C3F38&lt;/A&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 14 Jun 2023 03:20:52 GMT</pubDate>
    <dc:creator>Senlent</dc:creator>
    <dc:date>2023-06-14T03:20:52Z</dc:date>
    <item>
      <title>Chip deadlock</title>
      <link>https://community.nxp.com/t5/S32K/Chip-deadlock/m-p/1668418#M23900</link>
      <description>&lt;P&gt;Accidental operation to modify 0x40c to 0xff, how to deal with it&lt;/P&gt;</description>
      <pubDate>Tue, 13 Jun 2023 12:53:53 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/Chip-deadlock/m-p/1668418#M23900</guid>
      <dc:creator>zxc1</dc:creator>
      <dc:date>2023-06-13T12:53:53Z</dc:date>
    </item>
    <item>
      <title>Re: Chip deadlock</title>
      <link>https://community.nxp.com/t5/S32K/Chip-deadlock/m-p/1668826#M23918</link>
      <description>&lt;P&gt;&lt;A href="mailto:Hi@zxc1" target="_blank"&gt;Hi@zxc1&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;If you only modified this part, you can try to disable security using Mass Erase.&lt;BR /&gt;（Remember, if you use the CESc module and allocate CSEc with key, please do not try to use Mass Erase to erase the chip directly）&lt;/P&gt;
&lt;P&gt;1.if you're using PE&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Senlent_0-1686712133758.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/227526iB9A0277E680F4608/image-size/medium?v=v2&amp;amp;px=400" role="button" title="Senlent_0-1686712133758.png" alt="Senlent_0-1686712133758.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;2.J-Link&lt;/P&gt;
&lt;P&gt;&lt;A href="https://community.nxp.com/t5/S32K/S32K148-Unsecurity/m-p/1182938?lightbox-message-images-1176957=128885iE01BFC9C805C3F38" target="_self"&gt;https://community.nxp.com/t5/S32K/S32K148-Unsecurity/m-p/1182938?lightbox-message-images-1176957=128885iE01BFC9C805C3F38&lt;/A&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 14 Jun 2023 03:20:52 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/Chip-deadlock/m-p/1668826#M23918</guid>
      <dc:creator>Senlent</dc:creator>
      <dc:date>2023-06-14T03:20:52Z</dc:date>
    </item>
  </channel>
</rss>

