<?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のトピックMigrating from FreeRTOS to SafeRTOS on S32K34x</title>
    <link>https://community.nxp.com/t5/S32K/Migrating-from-FreeRTOS-to-SafeRTOS-on-S32K34x/m-p/2301486#M56402</link>
    <description>&lt;P&gt;We are currently using FreeRTOS in our code base and are migrating to SafeRTOS on #S32K3x&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Our code (with FreeRTOS) currently uses USING_OS_FREERTOS configuration for the OSIF layer. This allows the MCAL drivers to use different interrupt masking strategies based on context (BASEPRI in ISRs to allow higher-priority interrupts vs. PRIMASK in tasks). There is no official support for SafeRTOS while configuring the RTD/MCAL in S32 design studio,&amp;nbsp;so either the option is to use the FreeRTOS or to use the bare metal approach.&amp;nbsp;Configuring the NXP RTD OSIF layer with USING_OS_BAREMETAL, causes MCAL critical sections to use direct assembly instructions (cpsid i/cpsie i) without RTOS integration.&lt;BR /&gt;&lt;BR /&gt;I am wondering what the best approach is. Using:&lt;/P&gt;&lt;P&gt;- BAREMETAL mode with manual interrupt management.&lt;BR /&gt;- FREERTOS with some kind of compatibility layer or changing the OSIF code for RTOS-aware critical sections.&lt;BR /&gt;- A native SafeRTOS integration approach (if there is one).&lt;/P&gt;</description>
    <pubDate>Tue, 27 Jan 2026 19:42:01 GMT</pubDate>
    <dc:creator>abhishekpeak</dc:creator>
    <dc:date>2026-01-27T19:42:01Z</dc:date>
    <item>
      <title>Migrating from FreeRTOS to SafeRTOS on S32K34x</title>
      <link>https://community.nxp.com/t5/S32K/Migrating-from-FreeRTOS-to-SafeRTOS-on-S32K34x/m-p/2301486#M56402</link>
      <description>&lt;P&gt;We are currently using FreeRTOS in our code base and are migrating to SafeRTOS on #S32K3x&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Our code (with FreeRTOS) currently uses USING_OS_FREERTOS configuration for the OSIF layer. This allows the MCAL drivers to use different interrupt masking strategies based on context (BASEPRI in ISRs to allow higher-priority interrupts vs. PRIMASK in tasks). There is no official support for SafeRTOS while configuring the RTD/MCAL in S32 design studio,&amp;nbsp;so either the option is to use the FreeRTOS or to use the bare metal approach.&amp;nbsp;Configuring the NXP RTD OSIF layer with USING_OS_BAREMETAL, causes MCAL critical sections to use direct assembly instructions (cpsid i/cpsie i) without RTOS integration.&lt;BR /&gt;&lt;BR /&gt;I am wondering what the best approach is. Using:&lt;/P&gt;&lt;P&gt;- BAREMETAL mode with manual interrupt management.&lt;BR /&gt;- FREERTOS with some kind of compatibility layer or changing the OSIF code for RTOS-aware critical sections.&lt;BR /&gt;- A native SafeRTOS integration approach (if there is one).&lt;/P&gt;</description>
      <pubDate>Tue, 27 Jan 2026 19:42:01 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/Migrating-from-FreeRTOS-to-SafeRTOS-on-S32K34x/m-p/2301486#M56402</guid>
      <dc:creator>abhishekpeak</dc:creator>
      <dc:date>2026-01-27T19:42:01Z</dc:date>
    </item>
    <item>
      <title>Re: Migrating from FreeRTOS to SafeRTOS on S32K34x</title>
      <link>https://community.nxp.com/t5/S32K/Migrating-from-FreeRTOS-to-SafeRTOS-on-S32K34x/m-p/2301530#M56404</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/255893"&gt;@abhishekpeak&lt;/a&gt;.,&lt;/P&gt;
&lt;P&gt;You are correct, right now there is no&amp;nbsp;native SafeRTOS integration approach, and as far as I know, we have no plan to provide it for customer use. NXP mainly focuses on the RTD driver which support MCAL layer in AUTOSAR. It is customer's willingness to select third-party RTOS, stacks, IDEs, compilers, etc. for their project.&lt;/P&gt;
&lt;P&gt;Realistically, you could implement either approach for this, either baremetal or starting with FreeRTOS and eventually upgrading to SafeRTOS.&lt;/P&gt;
&lt;P&gt;I found this document regarding scalability and the S32K family:&amp;nbsp;&lt;A href="https://www.highintegritysystems.com/downloads/manuals_and_datasheets/S32K_SAFERTOS_Datasheet_v1.1.pdf" target="_self"&gt;S32K_SAFERTOS_Datasheet_v1.1.pdf&lt;/A&gt;.&lt;/P&gt;
&lt;P&gt;Of course, this means that integration should be done with the support of a third-party.&lt;/P&gt;
&lt;P&gt;Just as a note, you can also refer to&amp;nbsp;&lt;A href="https://nxp.flexnetoperations.com/control/frse/product?child_plneID=860247" target="_self"&gt;S32K3 - NXP RTOS.&lt;/A&gt;&amp;nbsp;The NXP RTOS is a real-time operating system which conforms to the AUTOSAR Specification of Operating System R21-11 rev. 0 specification. Since it is delivered by NXP, it is aligned with the RTD releases.&lt;/P&gt;
&lt;P&gt;Best regards,&lt;BR /&gt;Julián&lt;/P&gt;</description>
      <pubDate>Tue, 27 Jan 2026 22:09:41 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/Migrating-from-FreeRTOS-to-SafeRTOS-on-S32K34x/m-p/2301530#M56404</guid>
      <dc:creator>Julián_AragónM</dc:creator>
      <dc:date>2026-01-27T22:09:41Z</dc:date>
    </item>
  </channel>
</rss>

