<?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: Open SDA Firmware Question in S32K</title>
    <link>https://community.nxp.com/t5/S32K/Open-SDA-Firmware-Question/m-p/2398540#M60029</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/263485"&gt;@wj_kwak&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If the MK26 OpenSDA device has been overwritten via J13, the standard OpenSDA update procedure may no longer be applicable, since it relies on a functioning OpenSDA bootloader. The OpenSDA recovery firmware is not generally distributed as a standalone programming image.&lt;/P&gt;
&lt;P&gt;The OpenSDA firmware and bootloader are PEmicro technology rather than NXP-developed software. PEmicro provides the firmware updates, bootloader update applications, and related support for OpenSDA.&lt;/P&gt;
&lt;P&gt;Therefore, if the MK26 has been erased or reprogrammed via JTAG/SWD and the OpenSDA bootloader is no longer functional, PEmicro would be the primary contact for recovery guidance and firmware availability.&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.pemicro.com/support/index.cfm" target="_blank"&gt;https://www.pemicro.com/support/index.cfm&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;Lukas&lt;/P&gt;</description>
    <pubDate>Fri, 24 Jul 2026 05:26:23 GMT</pubDate>
    <dc:creator>lukaszadrapa</dc:creator>
    <dc:date>2026-07-24T05:26:23Z</dc:date>
    <item>
      <title>Open SDA Firmware Question</title>
      <link>https://community.nxp.com/t5/S32K/Open-SDA-Firmware-Question/m-p/2398022#M60006</link>
      <description>&lt;P&gt;I purchased the FRDM-A-S32K358 development board and checked the JTAG port for changing the firmware on the MK26 chip responsible for Open SDA. If I accidentally install the firmware on J13, I will need to obtain the Open SDA firmware. In this case, can I obtain the firmware by requesting it via a support ticket?&lt;/P&gt;</description>
      <pubDate>Thu, 23 Jul 2026 06:35:38 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/Open-SDA-Firmware-Question/m-p/2398022#M60006</guid>
      <dc:creator>wj_kwak</dc:creator>
      <dc:date>2026-07-23T06:35:38Z</dc:date>
    </item>
    <item>
      <title>Re: Open SDA Firmware Question</title>
      <link>https://community.nxp.com/t5/S32K/Open-SDA-Firmware-Question/m-p/2398540#M60029</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/263485"&gt;@wj_kwak&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If the MK26 OpenSDA device has been overwritten via J13, the standard OpenSDA update procedure may no longer be applicable, since it relies on a functioning OpenSDA bootloader. The OpenSDA recovery firmware is not generally distributed as a standalone programming image.&lt;/P&gt;
&lt;P&gt;The OpenSDA firmware and bootloader are PEmicro technology rather than NXP-developed software. PEmicro provides the firmware updates, bootloader update applications, and related support for OpenSDA.&lt;/P&gt;
&lt;P&gt;Therefore, if the MK26 has been erased or reprogrammed via JTAG/SWD and the OpenSDA bootloader is no longer functional, PEmicro would be the primary contact for recovery guidance and firmware availability.&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.pemicro.com/support/index.cfm" target="_blank"&gt;https://www.pemicro.com/support/index.cfm&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;Lukas&lt;/P&gt;</description>
      <pubDate>Fri, 24 Jul 2026 05:26:23 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/Open-SDA-Firmware-Question/m-p/2398540#M60029</guid>
      <dc:creator>lukaszadrapa</dc:creator>
      <dc:date>2026-07-24T05:26:23Z</dc:date>
    </item>
  </channel>
</rss>

