<?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>topic Re: S32 autosar in S32K</title>
    <link>https://community.nxp.com/t5/S32K/S32-autosar/m-p/2364580#M58538</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;BLOCKQUOTE&gt;
&lt;P&gt;Can S32DS + RTD alone generate AUTOSAR-compliant code?&lt;/P&gt;
&lt;/BLOCKQUOTE&gt;
&lt;P&gt;No.&lt;/P&gt;
&lt;P&gt;To be AUTOSAR-compliant, you must have:&lt;/P&gt;
&lt;P&gt;&lt;LI-EMOJI id="lia_white-heavy-check-mark" title=":white_heavy_check_mark:"&gt;&lt;/LI-EMOJI&gt; MCAL (drivers) → RTD can play this role&lt;BR /&gt;&lt;LI-EMOJI id="lia_cross-mark" title=":cross_mark:"&gt;&lt;/LI-EMOJI&gt; BSW stack (Com, DCM, NvM, etc.)&lt;BR /&gt;&lt;LI-EMOJI id="lia_cross-mark" title=":cross_mark:"&gt;&lt;/LI-EMOJI&gt; RTE (Runtime Environment)&lt;BR /&gt;&lt;LI-EMOJI id="lia_cross-mark" title=":cross_mark:"&gt;&lt;/LI-EMOJI&gt; ARXML-based configuration&lt;BR /&gt;&lt;LI-EMOJI id="lia_cross-mark" title=":cross_mark:"&gt;&lt;/LI-EMOJI&gt; System configuration tool (like tresos/DaVinci)&lt;/P&gt;
&lt;P&gt;These elements are mandatory in AUTOSAR architecture.&lt;/P&gt;
&lt;P&gt;Best regards,&lt;/P&gt;
&lt;P&gt;Peter&lt;/P&gt;</description>
    <pubDate>Wed, 13 May 2026 07:14:37 GMT</pubDate>
    <dc:creator>petervlna</dc:creator>
    <dc:date>2026-05-13T07:14:37Z</dc:date>
    <item>
      <title>S32 autosar</title>
      <link>https://community.nxp.com/t5/S32K/S32-autosar/m-p/2364441#M58531</link>
      <description>&lt;P&gt;Is it possible to generate AUTOSAR-compliant code only by using S32DS with the RTD package and without EB Tresos? If yes, what is the specific implementation method?&lt;/P&gt;</description>
      <pubDate>Wed, 13 May 2026 02:55:40 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/S32-autosar/m-p/2364441#M58531</guid>
      <dc:creator>dream_lostcity</dc:creator>
      <dc:date>2026-05-13T02:55:40Z</dc:date>
    </item>
    <item>
      <title>Re: S32 autosar</title>
      <link>https://community.nxp.com/t5/S32K/S32-autosar/m-p/2364580#M58538</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;BLOCKQUOTE&gt;
&lt;P&gt;Can S32DS + RTD alone generate AUTOSAR-compliant code?&lt;/P&gt;
&lt;/BLOCKQUOTE&gt;
&lt;P&gt;No.&lt;/P&gt;
&lt;P&gt;To be AUTOSAR-compliant, you must have:&lt;/P&gt;
&lt;P&gt;&lt;LI-EMOJI id="lia_white-heavy-check-mark" title=":white_heavy_check_mark:"&gt;&lt;/LI-EMOJI&gt; MCAL (drivers) → RTD can play this role&lt;BR /&gt;&lt;LI-EMOJI id="lia_cross-mark" title=":cross_mark:"&gt;&lt;/LI-EMOJI&gt; BSW stack (Com, DCM, NvM, etc.)&lt;BR /&gt;&lt;LI-EMOJI id="lia_cross-mark" title=":cross_mark:"&gt;&lt;/LI-EMOJI&gt; RTE (Runtime Environment)&lt;BR /&gt;&lt;LI-EMOJI id="lia_cross-mark" title=":cross_mark:"&gt;&lt;/LI-EMOJI&gt; ARXML-based configuration&lt;BR /&gt;&lt;LI-EMOJI id="lia_cross-mark" title=":cross_mark:"&gt;&lt;/LI-EMOJI&gt; System configuration tool (like tresos/DaVinci)&lt;/P&gt;
&lt;P&gt;These elements are mandatory in AUTOSAR architecture.&lt;/P&gt;
&lt;P&gt;Best regards,&lt;/P&gt;
&lt;P&gt;Peter&lt;/P&gt;</description>
      <pubDate>Wed, 13 May 2026 07:14:37 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/S32-autosar/m-p/2364580#M58538</guid>
      <dc:creator>petervlna</dc:creator>
      <dc:date>2026-05-13T07:14:37Z</dc:date>
    </item>
  </channel>
</rss>

