<?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のトピックRe: FreeRTOS Runtime analysis for S32K144</title>
    <link>https://community.nxp.com/t5/S32K/FreeRTOS-Runtime-analysis-for-S32K144/m-p/1570373#M19453</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;Please take a look at:&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.freertos.org/rtos-run-time-stats.html" target="_blank"&gt;https://www.freertos.org/rtos-run-time-stats.html&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;Example in the SDK does not use this feature. It’s up to users to implement it. It is possible to use any timer capable to generate periodic interrupt, so both LPIT and LPTMR can be utilized.&lt;/P&gt;
&lt;P&gt;Another option is to use some tracing tools in advanced debuggers to do the analysis. This is not supported by S32 Design Studio.&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;Lukas&lt;/P&gt;</description>
    <pubDate>Thu, 15 Dec 2022 10:19:21 GMT</pubDate>
    <dc:creator>lukaszadrapa</dc:creator>
    <dc:date>2022-12-15T10:19:21Z</dc:date>
    <item>
      <title>FreeRTOS Runtime analysis for S32K144</title>
      <link>https://community.nxp.com/t5/S32K/FreeRTOS-Runtime-analysis-for-S32K144/m-p/1569893#M19438</link>
      <description>&lt;P&gt;We want to analyze runtime and memory usage for each task configured using&amp;nbsp; FreeRTOS&lt;/P&gt;&lt;P&gt;Tick time is 1msec&lt;/P&gt;&lt;P&gt;PLL clk 8Mhz&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;How often the runtime is updated for each task and how it is achieved&lt;/LI&gt;&lt;LI&gt;Did you use ISR based mechanism to update task runtime for each timer tick (for eg 250us)&lt;/LI&gt;&lt;LI&gt;Which clock to be used ? LPTMR OR LPIT&lt;/LI&gt;&lt;LI&gt;any other API other than&amp;nbsp;vTaskGetRunTimeStats()&amp;nbsp;&lt;/LI&gt;&lt;/OL&gt;</description>
      <pubDate>Wed, 14 Dec 2022 17:11:22 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/FreeRTOS-Runtime-analysis-for-S32K144/m-p/1569893#M19438</guid>
      <dc:creator>Amichheda</dc:creator>
      <dc:date>2022-12-14T17:11:22Z</dc:date>
    </item>
    <item>
      <title>Re: FreeRTOS Runtime analysis for S32K144</title>
      <link>https://community.nxp.com/t5/S32K/FreeRTOS-Runtime-analysis-for-S32K144/m-p/1570373#M19453</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;Please take a look at:&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.freertos.org/rtos-run-time-stats.html" target="_blank"&gt;https://www.freertos.org/rtos-run-time-stats.html&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;Example in the SDK does not use this feature. It’s up to users to implement it. It is possible to use any timer capable to generate periodic interrupt, so both LPIT and LPTMR can be utilized.&lt;/P&gt;
&lt;P&gt;Another option is to use some tracing tools in advanced debuggers to do the analysis. This is not supported by S32 Design Studio.&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;Lukas&lt;/P&gt;</description>
      <pubDate>Thu, 15 Dec 2022 10:19:21 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/FreeRTOS-Runtime-analysis-for-S32K144/m-p/1570373#M19453</guid>
      <dc:creator>lukaszadrapa</dc:creator>
      <dc:date>2022-12-15T10:19:21Z</dc:date>
    </item>
  </channel>
</rss>

