<?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>S32KのトピックS32K Interrupt Monitor (INTM) Functionality Clarification</title>
    <link>https://community.nxp.com/t5/S32K/S32K-Interrupt-Monitor-INTM-Functionality-Clarification/m-p/2019125#M44573</link>
    <description>&lt;P&gt;We are implementing interrupt monitoring on the S32K platform and seek clarification on the INTM peripheral's measurement methodology and Timer register interpretation.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Specific Technical Questions:&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Measurement Methodology:&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Does the INTM measure the delta between consecutive interrupt occurrences, or&lt;/P&gt;&lt;P&gt;Does it measure the latency between interrupt assertion and the first instruction execution of the ISR?&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Timer Register Interpretation:&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;In our current implementation monitoring ADC and STM interrupts, we observe Timer register values ranging from 0xFE to 0x120.&lt;/P&gt;&lt;P&gt;Are these values representing raw clock cycles or a scaled time period?&lt;/P&gt;&lt;P&gt;What is the reference clock source for these measurements?&lt;/P&gt;&lt;P&gt;This information is critical for our interrupt latency optimization efforts and system timing analysis.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you for your assistance.&lt;/P&gt;</description>
    <pubDate>Tue, 24 Dec 2024 15:36:30 GMT</pubDate>
    <dc:creator>BalasubramaniyanS</dc:creator>
    <dc:date>2024-12-24T15:36:30Z</dc:date>
    <item>
      <title>S32K Interrupt Monitor (INTM) Functionality Clarification</title>
      <link>https://community.nxp.com/t5/S32K/S32K-Interrupt-Monitor-INTM-Functionality-Clarification/m-p/2019125#M44573</link>
      <description>&lt;P&gt;We are implementing interrupt monitoring on the S32K platform and seek clarification on the INTM peripheral's measurement methodology and Timer register interpretation.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Specific Technical Questions:&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Measurement Methodology:&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Does the INTM measure the delta between consecutive interrupt occurrences, or&lt;/P&gt;&lt;P&gt;Does it measure the latency between interrupt assertion and the first instruction execution of the ISR?&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Timer Register Interpretation:&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;In our current implementation monitoring ADC and STM interrupts, we observe Timer register values ranging from 0xFE to 0x120.&lt;/P&gt;&lt;P&gt;Are these values representing raw clock cycles or a scaled time period?&lt;/P&gt;&lt;P&gt;What is the reference clock source for these measurements?&lt;/P&gt;&lt;P&gt;This information is critical for our interrupt latency optimization efforts and system timing analysis.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you for your assistance.&lt;/P&gt;</description>
      <pubDate>Tue, 24 Dec 2024 15:36:30 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/S32K-Interrupt-Monitor-INTM-Functionality-Clarification/m-p/2019125#M44573</guid>
      <dc:creator>BalasubramaniyanS</dc:creator>
      <dc:date>2024-12-24T15:36:30Z</dc:date>
    </item>
    <item>
      <title>Re: S32K Interrupt Monitor (INTM) Functionality Clarification</title>
      <link>https://community.nxp.com/t5/S32K/S32K-Interrupt-Monitor-INTM-Functionality-Clarification/m-p/2019988#M44624</link>
      <description>&lt;P&gt;Hi&lt;/P&gt;
&lt;P&gt;&lt;SPAN data-teams="true"&gt;Due to the Christmas vacation period, our response times may be longer than usual. We appreciate your patience as our team navigates this busy season.&amp;nbsp;&lt;BR /&gt;Please be assured, we are committed to responding your inquiries as quickly as possible.&amp;nbsp;&lt;BR /&gt;Thank you for your understanding and happy holidays!&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN data-teams="true"&gt;Best Regards,&lt;BR /&gt;Robin&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 27 Dec 2024 08:54:28 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/S32K-Interrupt-Monitor-INTM-Functionality-Clarification/m-p/2019988#M44624</guid>
      <dc:creator>Robin_Shen</dc:creator>
      <dc:date>2024-12-27T08:54:28Z</dc:date>
    </item>
    <item>
      <title>Re: S32K Interrupt Monitor (INTM) Functionality Clarification</title>
      <link>https://community.nxp.com/t5/S32K/S32K-Interrupt-Monitor-INTM-Functionality-Clarification/m-p/2020251#M44645</link>
      <description>&lt;P&gt;Hi&lt;/P&gt;
&lt;P&gt;A1:&lt;FONT color="#808080"&gt; INTM allows you to set a maximum timer count for the interrupt latency from &lt;STRONG&gt;interrupt request&lt;/STRONG&gt; to &lt;STRONG&gt;interrupt acknowledge&lt;/STRONG&gt;.&lt;/FONT&gt; So if you write &lt;STRONG&gt;INTM_IACK&lt;/STRONG&gt; as the first instruction in your ISR, then it is what you said. (I&lt;SPAN&gt;t measure the latency between interrupt request and the first instruction execution of the ISR&lt;/SPAN&gt;)&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="INTM allows you to set a maximum timer count for the interrupt latency from interrupt request to interrupt acknowledge.png" style="width: 859px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/317551iF6FB2149DBFD543B/image-size/large?v=v2&amp;amp;px=999" role="button" title="INTM allows you to set a maximum timer count for the interrupt latency from interrupt request to interrupt acknowledge.png" alt="INTM allows you to set a maximum timer count for the interrupt latency from interrupt request to interrupt acknowledge.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;A2: &lt;FONT color="#808080"&gt;Counts the number of &lt;STRONG&gt;INTM clock cycles&lt;/STRONG&gt; for a detected interrupt request to an acknowledged interrupt processing.&amp;nbsp;&lt;/FONT&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="16.5.6 Timer for Monitor a (INTM_TIMER0 - INTM_TIMER3).png" style="width: 911px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/317559iC2F41D903877E6E7/image-size/large?v=v2&amp;amp;px=999" role="button" title="16.5.6 Timer for Monitor a (INTM_TIMER0 - INTM_TIMER3).png" alt="16.5.6 Timer for Monitor a (INTM_TIMER0 - INTM_TIMER3).png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;So this is related to the value of your &lt;STRONG&gt;AIPS_PLAT_CLK&lt;/STRONG&gt; frequency.&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Table 128. System module clocking INTM AIPS_PLAT_CLK.png" style="width: 867px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/317556i7B4B80957FF0E1B9/image-size/large?v=v2&amp;amp;px=999" role="button" title="Table 128. System module clocking INTM AIPS_PLAT_CLK.png" alt="Table 128. System module clocking INTM AIPS_PLAT_CLK.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;Best Regards,&lt;BR /&gt;Robin&lt;BR /&gt;-------------------------------------------------------------------------------&lt;BR /&gt;Note:&lt;BR /&gt;- If this post answers your question, please click the "ACCEPT AS SOLUTION" button. Thank you!&lt;/P&gt;
&lt;P&gt;- We are following threads for 7 weeks after the last post, later replies are ignored&lt;BR /&gt;Please open a new thread and refer to the closed one, if you have a related question at a later point in time.&lt;BR /&gt;-------------------------------------------------------------------------------&lt;/P&gt;</description>
      <pubDate>Mon, 30 Dec 2024 02:44:48 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/S32K-Interrupt-Monitor-INTM-Functionality-Clarification/m-p/2020251#M44645</guid>
      <dc:creator>Robin_Shen</dc:creator>
      <dc:date>2024-12-30T02:44:48Z</dc:date>
    </item>
  </channel>
</rss>

