<?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: Mass Erase through SWD without access to reset in Kinetis Microcontrollers</title>
    <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/Mass-Erase-through-SWD-without-access-to-reset/m-p/602105#M35372</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi guylejeune&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This is not possible to do, if SWD have not access to the reset pin, it cannot get hold the device, Jlink and PEmicro tools both have access to the reset pin, that why in that post and with PEMicro can do the mass erase. In the AN4358 application note they mentioned that you nee to &lt;EM&gt;keep the processor in reset, &lt;/EM&gt;this has to be done with the pin or with the&amp;nbsp;System Reset Request (when it is not secured). It works for you sometimes because the target is constantly resetting if you have not code to execute, so, sometimes you catch your devices in reset state.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For further information please check the following links:&lt;/P&gt;&lt;P&gt;&lt;A class="link-titled" href="https://mcuoneclipse.com/2012/11/04/how-not-to-secure-my-microcontroller/" title="https://mcuoneclipse.com/2012/11/04/how-not-to-secure-my-microcontroller/"&gt;How (not) to Secure my Microcontroller | MCU on Eclipse&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.nxp.com/thread/438151"&gt;Communication error while accessing MDM-AP&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Hope this information helps you&lt;BR /&gt;Have a great day,&lt;BR /&gt;Jorge Alcala&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 07 Mar 2017 00:56:13 GMT</pubDate>
    <dc:creator>jorge_a_vazquez</dc:creator>
    <dc:date>2017-03-07T00:56:13Z</dc:date>
    <item>
      <title>Mass Erase through SWD without access to reset</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/Mass-Erase-through-SWD-without-access-to-reset/m-p/602104#M35371</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;using a MK22, I face situations where the device is secured while it still can be mass-erased.&lt;/P&gt;&lt;P&gt;I have to recover through SWD commands, the boards used don't provide access to reset pin (which is connected to a pull-up).&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I know it is possible to recover this situation:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Using the procedure from AN4835, it works from times to times (1x50) ;&lt;/LI&gt;&lt;LI&gt;using a PEMICRO programming device achieves it ;&lt;/LI&gt;&lt;LI&gt;&lt;A _jive_internal="true" href="https://community.nxp.com/message/870775"&gt;This thread&lt;/A&gt; mentions it is possible, however without describing the steps to do so.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So I would like to achieve this in a deterministic ways.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Using the procedure of AN4835, I endup most of the time with &lt;/P&gt;&lt;UL&gt;&lt;LI&gt;CTRL [FMEIP] bit set indefinitely&lt;/LI&gt;&lt;LI&gt;STAT [FMEACK] is not acknowledge even though MEEN = 1&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What additional steps are required ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As pointed out by other users, the procedure described in AN4835 states&lt;/P&gt;&lt;BLOCKQUOTE class="jive_macro_quote jive-quote jive_text_macro"&gt;&lt;P&gt;It is important to ensure that the processor doesn't receive a new reset or execute any code that could interfere with the operation of the mass erase command while the mass erase is in progress. To avoid this, keep the processor in reset by keeping RESET asserted or keeping the System Reset Request set during the mass erase.&lt;/P&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;But, according to the Ref Manual of my chip, System Reset Request bit of MDM-AP Control Register is unavailable in secure mode.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So what extra steps are required for this procedure ?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 27 Feb 2017 18:21:37 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/Mass-Erase-through-SWD-without-access-to-reset/m-p/602104#M35371</guid>
      <dc:creator>guylejeune</dc:creator>
      <dc:date>2017-02-27T18:21:37Z</dc:date>
    </item>
    <item>
      <title>Re: Mass Erase through SWD without access to reset</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/Mass-Erase-through-SWD-without-access-to-reset/m-p/602105#M35372</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi guylejeune&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This is not possible to do, if SWD have not access to the reset pin, it cannot get hold the device, Jlink and PEmicro tools both have access to the reset pin, that why in that post and with PEMicro can do the mass erase. In the AN4358 application note they mentioned that you nee to &lt;EM&gt;keep the processor in reset, &lt;/EM&gt;this has to be done with the pin or with the&amp;nbsp;System Reset Request (when it is not secured). It works for you sometimes because the target is constantly resetting if you have not code to execute, so, sometimes you catch your devices in reset state.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For further information please check the following links:&lt;/P&gt;&lt;P&gt;&lt;A class="link-titled" href="https://mcuoneclipse.com/2012/11/04/how-not-to-secure-my-microcontroller/" title="https://mcuoneclipse.com/2012/11/04/how-not-to-secure-my-microcontroller/"&gt;How (not) to Secure my Microcontroller | MCU on Eclipse&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.nxp.com/thread/438151"&gt;Communication error while accessing MDM-AP&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Hope this information helps you&lt;BR /&gt;Have a great day,&lt;BR /&gt;Jorge Alcala&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 07 Mar 2017 00:56:13 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/Mass-Erase-through-SWD-without-access-to-reset/m-p/602105#M35372</guid>
      <dc:creator>jorge_a_vazquez</dc:creator>
      <dc:date>2017-03-07T00:56:13Z</dc:date>
    </item>
    <item>
      <title>Re: Mass Erase through SWD without access to reset</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/Mass-Erase-through-SWD-without-access-to-reset/m-p/602106#M35373</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Ok, I understand why it gave me the false impression it was possible.&lt;/P&gt;&lt;P&gt;Thanks for the information !&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 07 Mar 2017 16:16:42 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/Mass-Erase-through-SWD-without-access-to-reset/m-p/602106#M35373</guid>
      <dc:creator>guylejeune</dc:creator>
      <dc:date>2017-03-07T16:16:42Z</dc:date>
    </item>
  </channel>
</rss>

