<?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: Recovery mode for S32K328 in S32K</title>
    <link>https://community.nxp.com/t5/S32K/Recovery-mode-for-S32K328/m-p/2067924#M47132</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/248444"&gt;@MorcinM&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The recovery mode allows the host to recover from abnormal situations. There are two recovery modes: Secure Recovery Mode and JTAG-Based Recovery Mode.&lt;/P&gt;
&lt;P&gt;Secure Recovery Mode:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;In this mode, the HSE subsystem boots the Secure Recovery Application after its authenticity is confirmed against ADKP.&lt;/LI&gt;
&lt;LI&gt;This mode must be enabled using the HSE_SECURE_RECOVERY_CONFIG_ATTR_ID attribute. The start address and size of the secure recovery application must be provided in the IVT (Image Vector Table).&lt;/LI&gt;
&lt;LI&gt;When this mode is activated, the application core is released at the start address of the Secure Recovery Application.&lt;/LI&gt;
&lt;LI&gt;If Secure Recovery Mode fails, the device will automatically enter JTAG-Based Recovery Mode.&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;JTAG-Based Recovery Mode:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;In this mode, the HSE subsystem waits for a debugger connection (which must be authenticated when the LC is in OEM_PROD or IN_FIELD).&lt;/LI&gt;
&lt;LI&gt;Once the debugger is connected, the HSE releases the device from reset at a predefined address, JTAG_RECOVERY_START_ADDRESS, to a RAM-based application with the application core in sleep mode.&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;For more detailed information on these modes, refer to section 2.6.1.3 (Recovery Mode) of the HSE_B Firmware Reference Manual, Rev. 2.4.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;BR, VaneB&lt;/P&gt;</description>
    <pubDate>Tue, 25 Mar 2025 16:18:41 GMT</pubDate>
    <dc:creator>VaneB</dc:creator>
    <dc:date>2025-03-25T16:18:41Z</dc:date>
    <item>
      <title>Recovery mode for S32K328</title>
      <link>https://community.nxp.com/t5/S32K/Recovery-mode-for-S32K328/m-p/2067339#M47108</link>
      <description>&lt;P&gt;I am new in S32K3x programming. My question are:&lt;/P&gt;&lt;P&gt;1. Why this so called Recovery Mode is needed in therms of device programming/flashing? Isn't MCU always accessible using debugger or this can be restricted for production firmware and recovery mode is the only way to flash new firmware/reprogram&amp;nbsp; in that case?&lt;/P&gt;&lt;P&gt;2. For the device/MCU already in recovery mode: can be in that case the s32k328 programmed using JTAG or it supports also flashing via UART (meaning: NXP build in support for UART programming)?&lt;/P&gt;&lt;P&gt;Thanks in advance for your support.&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Marcin&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 24 Mar 2025 14:54:18 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/Recovery-mode-for-S32K328/m-p/2067339#M47108</guid>
      <dc:creator>MorcinM</dc:creator>
      <dc:date>2025-03-24T14:54:18Z</dc:date>
    </item>
    <item>
      <title>Re: Recovery mode for S32K328</title>
      <link>https://community.nxp.com/t5/S32K/Recovery-mode-for-S32K328/m-p/2067924#M47132</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/248444"&gt;@MorcinM&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The recovery mode allows the host to recover from abnormal situations. There are two recovery modes: Secure Recovery Mode and JTAG-Based Recovery Mode.&lt;/P&gt;
&lt;P&gt;Secure Recovery Mode:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;In this mode, the HSE subsystem boots the Secure Recovery Application after its authenticity is confirmed against ADKP.&lt;/LI&gt;
&lt;LI&gt;This mode must be enabled using the HSE_SECURE_RECOVERY_CONFIG_ATTR_ID attribute. The start address and size of the secure recovery application must be provided in the IVT (Image Vector Table).&lt;/LI&gt;
&lt;LI&gt;When this mode is activated, the application core is released at the start address of the Secure Recovery Application.&lt;/LI&gt;
&lt;LI&gt;If Secure Recovery Mode fails, the device will automatically enter JTAG-Based Recovery Mode.&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;JTAG-Based Recovery Mode:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;In this mode, the HSE subsystem waits for a debugger connection (which must be authenticated when the LC is in OEM_PROD or IN_FIELD).&lt;/LI&gt;
&lt;LI&gt;Once the debugger is connected, the HSE releases the device from reset at a predefined address, JTAG_RECOVERY_START_ADDRESS, to a RAM-based application with the application core in sleep mode.&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;For more detailed information on these modes, refer to section 2.6.1.3 (Recovery Mode) of the HSE_B Firmware Reference Manual, Rev. 2.4.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;BR, VaneB&lt;/P&gt;</description>
      <pubDate>Tue, 25 Mar 2025 16:18:41 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/Recovery-mode-for-S32K328/m-p/2067924#M47132</guid>
      <dc:creator>VaneB</dc:creator>
      <dc:date>2025-03-25T16:18:41Z</dc:date>
    </item>
  </channel>
</rss>

