topic Re: MassErase S32K118 never stops??? in S32K https://community.nxp.com/t5/S32K/MassErase-S32K118-never-stops/m-p/1060026#M7098 <HTML><HEAD></HEAD><BODY><P>Hello Pauli,</P><P></P><P>In the following section explains a reason why this bit is asserted in the MDM-AP register:</P><P><span class="lia-inline-image-display-wrapper" image-alt="pastedImage_1.png"><img src="https://community.nxp.com/t5/image/serverpage/image-id/109932i034BBE2FE695F3C1/image-size/large?v=v2&amp;px=999" role="button" title="pastedImage_1.png" alt="pastedImage_1.png" /></span></P><P>If the MCU is not secured it could be possible to recover from this state writing o the FSEC register but if this is the case it will be impossible to program again this MCU.</P><P></P><P>Best regards,</P><P>Alexis Andalon</P></BODY></HTML> Fri, 07 Aug 2020 18:22:58 GMT Alexis_A 2020-08-07T18:22:58Z MassErase S32K118 never stops??? https://community.nxp.com/t5/S32K/MassErase-S32K118-never-stops/m-p/1060025#M7097 <HTML><HEAD></HEAD><BODY><P>We have developed own SWD + GPIO bitbang SW to program onboard S32K118 MCU.</P><P></P><P>After performing SWD connection steps we have executed MassErase commands. Then the system left in some state that MDM-AP-CTRL registershows always 0x00000001 - MassErase is ongoing and memory access through AHB-AP is failing.</P><P></P><P><STRONG>## 0. DP Init</STRONG><BR />SWDReadDP 0x00&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; # returned 0x0BC11477<BR />SWDWriteDP 0x00 0x0000001E<BR />SWDWriteDP 0x01 0x00000000<BR />SWDWriteDP 0x01 0x50000000<BR />SWDReadDP 0x01&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; # returned 0xF0000040</P><P>## Reading ID's<BR />SWDWriteDP 0x02 0x010000F0<BR />SWDReadAP 0x03&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; # returned 0x00000000<BR />SWDReadDP 0x03&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; # returned 0x001C0020<BR />SWDWriteDP 0x02 0x000000F0<BR />SWDReadAP 0x03&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; # returned 0x00000000<BR />SWDReadDP 0x03&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; # returned 0x04770031<BR />#DP_ID&nbsp;&nbsp; = 0x0BC11477<BR />#AP_ID&nbsp;&nbsp; = 0x001C0020<BR />#AHB_ID&nbsp; = 0x04770031</P><P></P><P></P><P><STRONG>1. AN12130 MassErase</STRONG></P><P>SWDReadAP 0x00&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; # returned 0x00000000</P><P>SWDReadDP 0x03&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; # returned 0x00000034</P><P># MDM-AP Mass erase enabled</P><P>SWDWriteAP 0x01 0x00000009&nbsp; #MDM_AP_CTRL_MASS_ERASE | MDM_AP_CTRL_SYSTEM_RESET</P><P>SWDReadAP 0x01 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; # returned 0x00000001<BR />SWDReadDP 0x03&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; # returned 0x00000001</P><P>SWDReadAP 0x01 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; # returned 0x00000001<BR />SWDReadDP 0x03&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; # returned 0x00000001</P><P></P><P><STRONG>## AN12130 SWD connection steps</STRONG></P><P>SWDWriteDP 0x02 0x01000000<BR />SWDWriteAP 0x01 0x00000008<BR />SWDReadAP 0x00&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; # returned 0x00000001<BR />SWDReadDP 0x03&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; # returned 0x00000034<BR />...<BR />SWDReadAP 0x00&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; # returned 0x00000000<BR />SWDReadDP 0x03&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; # returned 0x0000003E&nbsp; # Flash is initialized</P><P></P><P>SWDReadAP 0x01&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; # returned 0x00000000<BR />SWDReadDP 0x03&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; # returned 0x00000001<BR />#MDM-AP ctrl: 0x00000001&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; # MassErase is ON???</P><P></P><P>#MDM-AP reset + debug request<BR />SWDWriteAP 0x01 0x0000000C<BR />#MDM-AP Clearing Reset<BR />SWDWriteAP 0x01 0x00000004</P><P></P><P>SWDReadDP 0x01&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; # returned 0xF0000040<BR />#DP_CTRL: 0xF0000040<BR />#DP_CTRL_READOK bit set</P><P></P><P>SWDWriteDP 0x02 0x01000000<BR />SWDReadAP 0x00&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; # returned 0x00000000<BR />SWDReadDP 0x03&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; # returned 0x00000034<BR />#MDM-AP Status: 0x00000034<BR />#System is secured.<BR />#System is in RESET<BR />#System can be mass erased</P><P></P><P>SWDReadAP 0x01&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; # returned 0x00000000<BR />SWDReadDP 0x03&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; # returned 0x00000001<BR />#MDM-AP Ctrl: 0x00000001<BR />#Mass erase is ON ???</P></BODY></HTML> Tue, 04 Aug 2020 08:47:13 GMT https://community.nxp.com/t5/S32K/MassErase-S32K118-never-stops/m-p/1060025#M7097 pavel_ 2020-08-04T08:47:13Z Re: MassErase S32K118 never stops??? https://community.nxp.com/t5/S32K/MassErase-S32K118-never-stops/m-p/1060026#M7098 <HTML><HEAD></HEAD><BODY><P>Hello Pauli,</P><P></P><P>In the following section explains a reason why this bit is asserted in the MDM-AP register:</P><P><span class="lia-inline-image-display-wrapper" image-alt="pastedImage_1.png"><img src="https://community.nxp.com/t5/image/serverpage/image-id/109932i034BBE2FE695F3C1/image-size/large?v=v2&amp;px=999" role="button" title="pastedImage_1.png" alt="pastedImage_1.png" /></span></P><P>If the MCU is not secured it could be possible to recover from this state writing o the FSEC register but if this is the case it will be impossible to program again this MCU.</P><P></P><P>Best regards,</P><P>Alexis Andalon</P></BODY></HTML> Fri, 07 Aug 2020 18:22:58 GMT https://community.nxp.com/t5/S32K/MassErase-S32K118-never-stops/m-p/1060026#M7098 Alexis_A 2020-08-07T18:22:58Z