<?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: VSCode + Autosar</title>
    <link>https://community.nxp.com/t5/S32K/VSCode-Autosar/m-p/2263424#M55445</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;Natively: NXP does not currently offer VS Code integration specifically tailored to S32K + AUTOSAR + MCAL (like EB Tresos/EB generated code).&lt;/P&gt;
&lt;P&gt;The closest entry point for NXP devices in VS Code is the MCUXpresso for VS Code extension, which supports Cortex‑M devices (like MCUXpresso SDK, Kinetis, LPC, i.MX RT), but it &lt;STRONG&gt;does not&lt;/STRONG&gt; &lt;STRONG&gt;explicitly support the S32K&lt;/STRONG&gt; family or integrate AUTOSAR MCAL features.&lt;/P&gt;
&lt;P&gt;Recommended Approach for S32K + AUTOSAR Development&lt;BR /&gt;For standard embedded development:&lt;/P&gt;
&lt;P&gt;Use MCUXpresso for VS Code for non-AUTOSAR work on other NXP MCU families.&amp;nbsp;No official, out-of-the-box VS Code + S32K + AUTOSAR support exists currently.&lt;/P&gt;
&lt;P&gt;For &lt;STRONG&gt;S32K&lt;/STRONG&gt;, use S32 Design Studio (Eclipse-based IDE) or the command-line toolchain delivered with S32DS and RTD.&lt;/P&gt;
&lt;P&gt;Best regards,&lt;/P&gt;
&lt;P&gt;Peter&lt;/P&gt;</description>
    <pubDate>Tue, 16 Dec 2025 08:05:20 GMT</pubDate>
    <dc:creator>petervlna</dc:creator>
    <dc:date>2025-12-16T08:05:20Z</dc:date>
    <item>
      <title>VSCode + Autosar</title>
      <link>https://community.nxp.com/t5/S32K/VSCode-Autosar/m-p/2262822#M55404</link>
      <description>&lt;P&gt;I am currently evaluating development environments for the NXP S32K platform and would prefer a solution based on Visual Studio Code, with native integration of S32K development tools and AUTOSAR enablement.&lt;/P&gt;&lt;P&gt;Could you please advise whether such an environment is currently available? If not, I would appreciate your recommendation for the most appropriate software development approach for AUTOSAR-based development targeting S32K devices.&lt;/P&gt;</description>
      <pubDate>Mon, 15 Dec 2025 12:04:54 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/VSCode-Autosar/m-p/2262822#M55404</guid>
      <dc:creator>erikraynolds</dc:creator>
      <dc:date>2025-12-15T12:04:54Z</dc:date>
    </item>
    <item>
      <title>Re: VSCode + Autosar</title>
      <link>https://community.nxp.com/t5/S32K/VSCode-Autosar/m-p/2263424#M55445</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;Natively: NXP does not currently offer VS Code integration specifically tailored to S32K + AUTOSAR + MCAL (like EB Tresos/EB generated code).&lt;/P&gt;
&lt;P&gt;The closest entry point for NXP devices in VS Code is the MCUXpresso for VS Code extension, which supports Cortex‑M devices (like MCUXpresso SDK, Kinetis, LPC, i.MX RT), but it &lt;STRONG&gt;does not&lt;/STRONG&gt; &lt;STRONG&gt;explicitly support the S32K&lt;/STRONG&gt; family or integrate AUTOSAR MCAL features.&lt;/P&gt;
&lt;P&gt;Recommended Approach for S32K + AUTOSAR Development&lt;BR /&gt;For standard embedded development:&lt;/P&gt;
&lt;P&gt;Use MCUXpresso for VS Code for non-AUTOSAR work on other NXP MCU families.&amp;nbsp;No official, out-of-the-box VS Code + S32K + AUTOSAR support exists currently.&lt;/P&gt;
&lt;P&gt;For &lt;STRONG&gt;S32K&lt;/STRONG&gt;, use S32 Design Studio (Eclipse-based IDE) or the command-line toolchain delivered with S32DS and RTD.&lt;/P&gt;
&lt;P&gt;Best regards,&lt;/P&gt;
&lt;P&gt;Peter&lt;/P&gt;</description>
      <pubDate>Tue, 16 Dec 2025 08:05:20 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/VSCode-Autosar/m-p/2263424#M55445</guid>
      <dc:creator>petervlna</dc:creator>
      <dc:date>2025-12-16T08:05:20Z</dc:date>
    </item>
  </channel>
</rss>

