<?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: mex config generate code different from windows and linux in S32K</title>
    <link>https://community.nxp.com/t5/S32K/mex-config-generate-code-different-from-windows-and-linux/m-p/2396904#M59953</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/264733"&gt;@Litten&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Currently, RTDs are supported only on the Windows platform and are not officially supported on Linux. Even if you are able to install them on Linux, you may encounter additional issues during development and integration.&lt;/P&gt;
&lt;P&gt;One of the main reasons is that Linux is a case-sensitive operating system,&amp;nbsp; details about this situation have been discussed in the thread &lt;A href="https://community.nxp.com/t5/S32-SDK/Problems-with-Lpi2c-Ip-MasterConfig-and-Lpi2c-Ip-SlaveState/td-p/1379173" target="_blank" rel="noopener"&gt;Problems with Lpi2c_Ip_MasterConfig and Lpi2c_Ip_SlaveState struct generation on S32DS for S32K344&lt;/A&gt;.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;BR, VaneB&lt;/P&gt;</description>
    <pubDate>Mon, 20 Jul 2026 18:23:30 GMT</pubDate>
    <dc:creator>VaneB</dc:creator>
    <dc:date>2026-07-20T18:23:30Z</dc:date>
    <item>
      <title>mex config generate code different from windows and linux</title>
      <link>https://community.nxp.com/t5/S32K/mex-config-generate-code-different-from-windows-and-linux/m-p/2396694#M59939</link>
      <description>&lt;P&gt;The same XEM file generates different code on different systems.&lt;BR /&gt;Windows&amp;nbsp; file generate code normal but linux system generate abnormal&lt;BR /&gt;&lt;SPAN class=""&gt;&lt;SPAN&gt;precondition&lt;/SPAN&gt;&lt;/SPAN&gt;：the same as RTD and SDK version install&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="5.jpg" style="width: 999px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/392639i439E0D377D2E1ABC/image-size/large?v=v2&amp;amp;px=999" role="button" title="5.jpg" alt="5.jpg" /&gt;&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 20 Jul 2026 07:55:20 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/mex-config-generate-code-different-from-windows-and-linux/m-p/2396694#M59939</guid>
      <dc:creator>Litten</dc:creator>
      <dc:date>2026-07-20T07:55:20Z</dc:date>
    </item>
    <item>
      <title>Re: mex config generate code different from windows and linux</title>
      <link>https://community.nxp.com/t5/S32K/mex-config-generate-code-different-from-windows-and-linux/m-p/2396904#M59953</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/264733"&gt;@Litten&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Currently, RTDs are supported only on the Windows platform and are not officially supported on Linux. Even if you are able to install them on Linux, you may encounter additional issues during development and integration.&lt;/P&gt;
&lt;P&gt;One of the main reasons is that Linux is a case-sensitive operating system,&amp;nbsp; details about this situation have been discussed in the thread &lt;A href="https://community.nxp.com/t5/S32-SDK/Problems-with-Lpi2c-Ip-MasterConfig-and-Lpi2c-Ip-SlaveState/td-p/1379173" target="_blank" rel="noopener"&gt;Problems with Lpi2c_Ip_MasterConfig and Lpi2c_Ip_SlaveState struct generation on S32DS for S32K344&lt;/A&gt;.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;BR, VaneB&lt;/P&gt;</description>
      <pubDate>Mon, 20 Jul 2026 18:23:30 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/mex-config-generate-code-different-from-windows-and-linux/m-p/2396904#M59953</guid>
      <dc:creator>VaneB</dc:creator>
      <dc:date>2026-07-20T18:23:30Z</dc:date>
    </item>
  </channel>
</rss>

