<?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 recover S32K148 while debugger can not connect to target in S32K</title>
    <link>https://community.nxp.com/t5/S32K/How-to-recover-S32K148-while-debugger-can-not-connect-to-target/m-p/852885#M3575</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Marcin,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have a S32K148 EVB that won't&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;connect to either PE Micro or J-Link after running firmware that may have misconfigured the flash. I also tried the same four techniques that you tried to unbrick it. Did you a find a solution to recover your system?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;&lt;P&gt;Paul&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 06 Sep 2019 18:57:43 GMT</pubDate>
    <dc:creator>pchui</dc:creator>
    <dc:date>2019-09-06T18:57:43Z</dc:date>
    <item>
      <title>How to recover S32K148 while debugger can not connect to target</title>
      <link>https://community.nxp.com/t5/S32K/How-to-recover-S32K148-while-debugger-can-not-connect-to-target/m-p/852884#M3574</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;My image builder tool has created wrong srec binary. After flashing one it is impossible to connect to S32K148 (using J-Link and P&amp;amp;E micro).&lt;/P&gt;&lt;P&gt;I have already tried:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;"Emergency Kinetis Device Recover by Full Chip Erase" option with P&amp;amp;E and S32DS&lt;/LI&gt;&lt;LI&gt;"Kinetis_Recovery_Utility" with P&amp;amp;E does not do the trick for me.&lt;/LI&gt;&lt;LI&gt;"unlock kinetis" from J-Commander or J-Flash can not erase flash.&lt;/LI&gt;&lt;LI&gt;J-Link command with the script (erase_all_pin.jlk) from topic:&amp;nbsp;&lt;A _jive_internal="true" class="link-titled" href="https://community.nxp.com/thread/439921?commentID=857127#comment-857127" title="https://community.nxp.com/thread/439921?commentID=857127#comment-857127"&gt;https://community.nxp.com/thread/439921?commentID=857127#comment-857127&lt;/A&gt;&amp;nbsp;can not solve the issue (full logs attached):&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;From&amp;nbsp;MDM-AP Status register (0x34) looks like System is in reset state, system security is enabled and fortunately mass erase is still enabled. I find that mass erase is not working because "Flash memory ready" bit is not set. I assume it is because from some reason processor did not boot.&lt;/P&gt;&lt;P&gt;Is it possible to somehow rescue this chip in this circumstances? What else can I check?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 22 Jan 2019 16:02:18 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/How-to-recover-S32K148-while-debugger-can-not-connect-to-target/m-p/852884#M3574</guid>
      <dc:creator>marcin_krzemins</dc:creator>
      <dc:date>2019-01-22T16:02:18Z</dc:date>
    </item>
    <item>
      <title>Re: How to recover S32K148 while debugger can not connect to target</title>
      <link>https://community.nxp.com/t5/S32K/How-to-recover-S32K148-while-debugger-can-not-connect-to-target/m-p/852885#M3575</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Marcin,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have a S32K148 EVB that won't&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;connect to either PE Micro or J-Link after running firmware that may have misconfigured the flash. I also tried the same four techniques that you tried to unbrick it. Did you a find a solution to recover your system?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;&lt;P&gt;Paul&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 06 Sep 2019 18:57:43 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/How-to-recover-S32K148-while-debugger-can-not-connect-to-target/m-p/852885#M3575</guid>
      <dc:creator>pchui</dc:creator>
      <dc:date>2019-09-06T18:57:43Z</dc:date>
    </item>
  </channel>
</rss>

