<?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>Embedded Software and Tools ClinicのトピックRe: Query on porting Azure RTOS to S32K344</title>
    <link>https://community.nxp.com/t5/Embedded-Software-and-Tools/Query-on-porting-Azure-RTOS-to-S32K344/m-p/2296126#M609</link>
    <description>&lt;P&gt;To get a 1 ms SysTick tick, you need to calculate and set the correct SysTick reload value based on your system clock. Determine the actual core/system clock frequency, then set:&lt;/P&gt;&lt;P&gt;Reload = (SysTick clock frequency × 0.001) − 1&lt;/P&gt;&lt;P&gt;Just like how you would rely on trusted &lt;A href="https://www.jnlelectric.com/" target="_self"&gt;JNL Electrical contractors in Houston&lt;/A&gt; for precise work, setting the exact reload value and clock source is critical for accurate timing. Updating only tx_initialize_low_level.s or clock settings won’t change the interval if the reload value isn’t adjusted. Once the reload value matches this calculation, your SysTickHandler will fire every 1 ms.&lt;/P&gt;</description>
    <pubDate>Mon, 19 Jan 2026 17:58:16 GMT</pubDate>
    <dc:creator>yisey</dc:creator>
    <dc:date>2026-01-19T17:58:16Z</dc:date>
    <item>
      <title>Query on porting Azure RTOS to S32K344</title>
      <link>https://community.nxp.com/t5/Embedded-Software-and-Tools/Query-on-porting-Azure-RTOS-to-S32K344/m-p/1885406#M496</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp;I am working on porting Azure RTOS to S32K344. I see that SysTickHandler is called every 167 micro seconds. Our requirement is 1ms Systick time. I tried changing clock settings in S32DS and also SYSTEM_CLK settings in&amp;nbsp;tx_initialize_low_level.s but there is no change in the SysTickHandler frequency, its constant at 167 micro seconds. Could you suggest me on this to achieve 1ms tick time?&amp;nbsp;&lt;/P&gt;&lt;P&gt;Please find clock settings screenshots in attachment.&lt;/P&gt;</description>
      <pubDate>Tue, 11 Jun 2024 18:03:10 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Embedded-Software-and-Tools/Query-on-porting-Azure-RTOS-to-S32K344/m-p/1885406#M496</guid>
      <dc:creator>vishwadn</dc:creator>
      <dc:date>2024-06-11T18:03:10Z</dc:date>
    </item>
    <item>
      <title>Re: Query on porting Azure RTOS to S32K344</title>
      <link>https://community.nxp.com/t5/Embedded-Software-and-Tools/Query-on-porting-Azure-RTOS-to-S32K344/m-p/2296126#M609</link>
      <description>&lt;P&gt;To get a 1 ms SysTick tick, you need to calculate and set the correct SysTick reload value based on your system clock. Determine the actual core/system clock frequency, then set:&lt;/P&gt;&lt;P&gt;Reload = (SysTick clock frequency × 0.001) − 1&lt;/P&gt;&lt;P&gt;Just like how you would rely on trusted &lt;A href="https://www.jnlelectric.com/" target="_self"&gt;JNL Electrical contractors in Houston&lt;/A&gt; for precise work, setting the exact reload value and clock source is critical for accurate timing. Updating only tx_initialize_low_level.s or clock settings won’t change the interval if the reload value isn’t adjusted. Once the reload value matches this calculation, your SysTickHandler will fire every 1 ms.&lt;/P&gt;</description>
      <pubDate>Mon, 19 Jan 2026 17:58:16 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Embedded-Software-and-Tools/Query-on-porting-Azure-RTOS-to-S32K344/m-p/2296126#M609</guid>
      <dc:creator>yisey</dc:creator>
      <dc:date>2026-01-19T17:58:16Z</dc:date>
    </item>
  </channel>
</rss>

