<?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>i.MX RT Crossover MCUsのトピックRe: ThreadX Interrupt latency</title>
    <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/ThreadX-Interrupt-latency/m-p/1495261#M20802</link>
    <description>&lt;P&gt;Hi Michael:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Please refer to below application note for RT interrupt latency.&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.nxp.com.cn/docs/en/application-note/AN12078.pdf" target="_blank"&gt;https://www.nxp.com.cn/docs/en/application-note/AN12078.pdf&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;For AzureRTOS interrupt latency.&amp;nbsp; I would suggest you post your question on our partner‘s community support.&lt;/P&gt;
&lt;P&gt;&lt;A href="https://azure.microsoft.com/en-us/support/community/" target="_blank"&gt;https://azure.microsoft.com/en-us/support/community/&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards&lt;/P&gt;
&lt;P&gt;Daniel&lt;/P&gt;</description>
    <pubDate>Tue, 26 Jul 2022 05:44:50 GMT</pubDate>
    <dc:creator>danielchen</dc:creator>
    <dc:date>2022-07-26T05:44:50Z</dc:date>
    <item>
      <title>ThreadX Interrupt latency</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/ThreadX-Interrupt-latency/m-p/1490548#M20646</link>
      <description>&lt;P&gt;Hello,&lt;BR /&gt;I have written an ISR that calls tx_semaphore_put() to wake a thread that is waiting for the semaphore using tx_semaphore_get(). There is only the one thread on the system. It takes 5 micro seconds for the thread to begin running. This is too long. How do I ensure my high priority interrupts are handled in a timely manner? Thanks.&lt;/P&gt;</description>
      <pubDate>Sat, 16 Jul 2022 00:52:09 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/ThreadX-Interrupt-latency/m-p/1490548#M20646</guid>
      <dc:creator>michaeldkfowler</dc:creator>
      <dc:date>2022-07-16T00:52:09Z</dc:date>
    </item>
    <item>
      <title>Re: ThreadX Interrupt latency</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/ThreadX-Interrupt-latency/m-p/1495261#M20802</link>
      <description>&lt;P&gt;Hi Michael:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Please refer to below application note for RT interrupt latency.&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.nxp.com.cn/docs/en/application-note/AN12078.pdf" target="_blank"&gt;https://www.nxp.com.cn/docs/en/application-note/AN12078.pdf&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;For AzureRTOS interrupt latency.&amp;nbsp; I would suggest you post your question on our partner‘s community support.&lt;/P&gt;
&lt;P&gt;&lt;A href="https://azure.microsoft.com/en-us/support/community/" target="_blank"&gt;https://azure.microsoft.com/en-us/support/community/&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards&lt;/P&gt;
&lt;P&gt;Daniel&lt;/P&gt;</description>
      <pubDate>Tue, 26 Jul 2022 05:44:50 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/ThreadX-Interrupt-latency/m-p/1495261#M20802</guid>
      <dc:creator>danielchen</dc:creator>
      <dc:date>2022-07-26T05:44:50Z</dc:date>
    </item>
  </channel>
</rss>

