<?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: Pending HSE response in S32K</title>
    <link>https://community.nxp.com/t5/S32K/Pending-HSE-response/m-p/2392357#M59749</link>
    <description>&lt;P&gt;We are not aware of a known S32K312 OTA issue that causes HSE services to remain permanently pending.&lt;BR /&gt;In general, every HSE service request should return a response. If no response is received, it may indicate that the HSE firmware encountered a fatal error and entered shutdown mode. In this case, we recommend checking the MU GSR register for diagnostic information.&lt;BR /&gt;Possible causes include invalid service parameters, invalid memory addresses, XRDC access violations, ECC errors, clock or initialization issues, resource conflicts, or other fatal HSE internal errors.&lt;BR /&gt;To help investigate, please provide the HSE FW version, the specific HSE service being executed, the service descriptor, and the MU status registers (FSR/GSR) when the issue occurs.&lt;/P&gt;</description>
    <pubDate>Wed, 08 Jul 2026 11:54:00 GMT</pubDate>
    <dc:creator>davidtosenovjan</dc:creator>
    <dc:date>2026-07-08T11:54:00Z</dc:date>
    <item>
      <title>Pending HSE response</title>
      <link>https://community.nxp.com/t5/S32K/Pending-HSE-response/m-p/2391879#M59738</link>
      <description>&lt;P&gt;I would like to inquire if there have been previous instances where the HSE response remained pending and did not arrive during an OTA update with the S32K312 MCU.&lt;/P&gt;&lt;P&gt;Additionally, please confirm under what circumstances the HSE response might become pending.&lt;/P&gt;</description>
      <pubDate>Wed, 08 Jul 2026 01:42:55 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/Pending-HSE-response/m-p/2391879#M59738</guid>
      <dc:creator>hjkim84</dc:creator>
      <dc:date>2026-07-08T01:42:55Z</dc:date>
    </item>
    <item>
      <title>Re: Pending HSE response</title>
      <link>https://community.nxp.com/t5/S32K/Pending-HSE-response/m-p/2392357#M59749</link>
      <description>&lt;P&gt;We are not aware of a known S32K312 OTA issue that causes HSE services to remain permanently pending.&lt;BR /&gt;In general, every HSE service request should return a response. If no response is received, it may indicate that the HSE firmware encountered a fatal error and entered shutdown mode. In this case, we recommend checking the MU GSR register for diagnostic information.&lt;BR /&gt;Possible causes include invalid service parameters, invalid memory addresses, XRDC access violations, ECC errors, clock or initialization issues, resource conflicts, or other fatal HSE internal errors.&lt;BR /&gt;To help investigate, please provide the HSE FW version, the specific HSE service being executed, the service descriptor, and the MU status registers (FSR/GSR) when the issue occurs.&lt;/P&gt;</description>
      <pubDate>Wed, 08 Jul 2026 11:54:00 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/Pending-HSE-response/m-p/2392357#M59749</guid>
      <dc:creator>davidtosenovjan</dc:creator>
      <dc:date>2026-07-08T11:54:00Z</dc:date>
    </item>
  </channel>
</rss>

