<?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>S32K中的主题 Re: Memory protection registers NXP</title>
    <link>https://community.nxp.com/t5/S32K/Memory-protection-registers-NXP/m-p/1046859#M6871</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Guru,&lt;/P&gt;&lt;P&gt;0x00 at 0x40C means that the MCU is secure but Mass Erase is enabled.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/94032i3AD9A942D4BD928E/image-size/large?v=v2&amp;amp;px=999" title="pastedImage_1.png" alt="pastedImage_1.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;So, the debugger should be able to mass erase the MCU unless there is another issue like allocated CSEc keys.&lt;/P&gt;&lt;P&gt;&lt;A class="link-titled" href="https://www.nxp.com/docs/en/application-note/AN12130.pdf" title="https://www.nxp.com/docs/en/application-note/AN12130.pdf"&gt;AN12130&amp;nbsp;Production Flash Programming Best Practices for S32K1xx MCUs&amp;nbsp;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/106118i57A641B067BEF8EC/image-size/large?v=v2&amp;amp;px=999" title="pastedImage_1.png" alt="pastedImage_1.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;BR, Daniel&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sun, 12 Apr 2020 11:47:18 GMT</pubDate>
    <dc:creator>danielmartynek</dc:creator>
    <dc:date>2020-04-12T11:47:18Z</dc:date>
    <item>
      <title>Memory protection registers NXP</title>
      <link>https://community.nxp.com/t5/S32K/Memory-protection-registers-NXP/m-p/1046856#M6868</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am working on S32K148 chip and had accidentally written the&amp;nbsp;Program Flash Protection Registers (FPROT0 - FPROT3) with 0. Post this, I couldn't program the chip through debugger.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is there a way where this protection can be removed through design studio utility, since even the JTAG connection is not possible post this?&amp;nbsp;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 01 Apr 2020 15:01:21 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/Memory-protection-registers-NXP/m-p/1046856#M6868</guid>
      <dc:creator>sgp_118</dc:creator>
      <dc:date>2020-04-01T15:01:21Z</dc:date>
    </item>
    <item>
      <title>Re: Memory protection registers NXP</title>
      <link>https://community.nxp.com/t5/S32K/Memory-protection-registers-NXP/m-p/1046857#M6869</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi&amp;nbsp;&lt;A class="jx-jive-macro-user" href="https://community.nxp.com/people/sgp_118"&gt;sgp_118&lt;/A&gt;,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Did you rewrite the FPROT registers or the FPROT bytes in the Flash configuration field?&lt;/P&gt;&lt;P&gt;Either way, if you FSEC_MEEN is not disabled, you should be able to mass erase the MCU.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;S32K1xx RM rev.12&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/97661i376667A123E415A8/image-size/large?v=v2&amp;amp;px=999" title="pastedImage_3.png" alt="pastedImage_3.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.nxp.com/docs/en/application-note/AN12130.pdf"&gt;AN12130 Production Flash Programming Best Practices for S32K1xxMCUs&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/99432iEDF6E4906446084D/image-size/large?v=v2&amp;amp;px=999" title="pastedImage_6.png" alt="pastedImage_6.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What debugger do you have?&lt;/P&gt;&lt;P&gt;And what error message do get from the IDE when the debugger is connecting?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;BR, Daniel&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 03 Apr 2020 10:36:55 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/Memory-protection-registers-NXP/m-p/1046857#M6869</guid>
      <dc:creator>danielmartynek</dc:creator>
      <dc:date>2020-04-03T10:36:55Z</dc:date>
    </item>
    <item>
      <title>Re: Memory protection registers NXP</title>
      <link>https://community.nxp.com/t5/S32K/Memory-protection-registers-NXP/m-p/1046858#M6870</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;Unfortunately all the registers in the region 0x400 - 0x40C are overwritten with 0s in the board&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am using S32K DS with P&amp;amp;E micro debugger.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Guru&lt;span class="lia-inline-image-display-wrapper"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/104333i5A9F42FFC4D55922/image-size/large?v=v2&amp;amp;px=999" title="P&amp;amp;E_Error.png" alt="P&amp;amp;E_Error.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 06 Apr 2020 14:26:24 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/Memory-protection-registers-NXP/m-p/1046858#M6870</guid>
      <dc:creator>sgp_118</dc:creator>
      <dc:date>2020-04-06T14:26:24Z</dc:date>
    </item>
    <item>
      <title>Re: Memory protection registers NXP</title>
      <link>https://community.nxp.com/t5/S32K/Memory-protection-registers-NXP/m-p/1046859#M6871</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Guru,&lt;/P&gt;&lt;P&gt;0x00 at 0x40C means that the MCU is secure but Mass Erase is enabled.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/94032i3AD9A942D4BD928E/image-size/large?v=v2&amp;amp;px=999" title="pastedImage_1.png" alt="pastedImage_1.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;So, the debugger should be able to mass erase the MCU unless there is another issue like allocated CSEc keys.&lt;/P&gt;&lt;P&gt;&lt;A class="link-titled" href="https://www.nxp.com/docs/en/application-note/AN12130.pdf" title="https://www.nxp.com/docs/en/application-note/AN12130.pdf"&gt;AN12130&amp;nbsp;Production Flash Programming Best Practices for S32K1xx MCUs&amp;nbsp;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/106118i57A641B067BEF8EC/image-size/large?v=v2&amp;amp;px=999" title="pastedImage_1.png" alt="pastedImage_1.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;BR, Daniel&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 12 Apr 2020 11:47:18 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/Memory-protection-registers-NXP/m-p/1046859#M6871</guid>
      <dc:creator>danielmartynek</dc:creator>
      <dc:date>2020-04-12T11:47:18Z</dc:date>
    </item>
  </channel>
</rss>

