<?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: S32K3x4EVB-T172 PIL Communication Error/ Timeout with MBDT S32K3xx 1.4.0 in Model-Based Design Toolbox (MBDT)</title>
    <link>https://community.nxp.com/t5/Model-Based-Design-Toolbox-MBDT/S32K3x4EVB-T172-PIL-Communication-Error-Timeout-with-MBDT/m-p/2409937#M10813</link>
    <description>&lt;P&gt;Hi,&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/265798"&gt;@PruthviB&lt;/a&gt;,&lt;/P&gt;
&lt;DIV&gt;
&lt;P&gt;Before investigating further, could you clarify why you are using &lt;STRONG&gt;MBDT S32K3xx v1.4.0&lt;/STRONG&gt;? The latest available release is &lt;STRONG&gt;v1.8.0&lt;/STRONG&gt;, which includes several fixes and improvements. We recommend upgrading to v1.8.0 first and checking whether the issue still reproduces.&lt;/P&gt;
&lt;P&gt;Regarding your setup, an &lt;STRONG&gt;external USB-to-Serial converter is not required for PIL communication&lt;/STRONG&gt; on the &lt;STRONG&gt;S32K3X4EVB-T172&lt;/STRONG&gt;. The onboard &lt;STRONG&gt;OpenSDA interface already provides access to the target UART used for host-target communication&lt;/STRONG&gt;, so the same USB connection can be used for both programming and PIL communication.&lt;/P&gt;
&lt;P&gt;Since OpenSDA has direct access to the UART pins, connecting an additional USB-to-Serial adapter is generally unnecessary and may even introduce configuration conflicts if multiple serial interfaces are active.&lt;/P&gt;
&lt;P&gt;Could you please try the example with:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;MBDT S32K3xx &lt;STRONG&gt;v1.8.0&lt;/STRONG&gt;&lt;/LI&gt;
&lt;LI&gt;Only the onboard &lt;STRONG&gt;OpenSDA USB connection&lt;/STRONG&gt;&lt;/LI&gt;
&lt;LI&gt;The COM port exposed by OpenSDA selected in the hardware settings&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Best regards,&lt;BR /&gt;Dragos&lt;/P&gt;
&lt;/DIV&gt;</description>
    <pubDate>Tue, 01 Sep 2026 07:47:33 GMT</pubDate>
    <dc:creator>dragostoma</dc:creator>
    <dc:date>2026-09-01T07:47:33Z</dc:date>
    <item>
      <title>S32K3x4EVB-T172 PIL Communication Error/ Timeout with MBDT S32K3xx 1.4.0</title>
      <link>https://community.nxp.com/t5/Model-Based-Design-Toolbox-MBDT/S32K3x4EVB-T172-PIL-Communication-Error-Timeout-with-MBDT/m-p/2409795#M10811</link>
      <description>&lt;P&gt;Hello,&amp;nbsp;&lt;/P&gt;&lt;P&gt;I tried running the example PIL S32CT with MBDT S32K3xx (v1.4.0) on MATLAB 2023a. My setup consists of an S32K3x4EVB-T172 connected via the onboard OpenSDA port.&lt;BR /&gt;&lt;BR /&gt;Attempt 1 (OpenSDA COM):&lt;BR /&gt;I can flash the generated target model successfully, but PIL execution fails immediately with the following error:&lt;BR /&gt;"The communication channel could not be opened" (see attached screen shot of the error message)&lt;BR /&gt;&lt;BR /&gt;Attempt 2 (External USB2Serial Convertor)&lt;BR /&gt;I kept the OpenSDA port connected for flashing, but connected an external USB2Sireal&amp;nbsp; connector to J44(1 to TX and 2 to RX) for PIL communication and updated the COM port in the hardware settings. The model flashes successfully, but execution times out with this error:&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Error: The timeout of 10 seconds for receiving data from the rtiostream interface has been exceeded. There might be multiple reasons for this communications failure.&lt;BR /&gt;You should:&lt;BR /&gt;&lt;BR /&gt;(a) Check that the target hardware configuration is correct, for example, check that the byte ordering is correct.&lt;BR /&gt;(b) Confirm that the target application is running on the target hardware.&lt;BR /&gt;(c) Consider the possibility of application run-time failures (e.g. divide by zero exceptions, incorrect custom code integration, etc.).&lt;BR /&gt;&lt;BR /&gt;Note (c): To identify possible reasons for the run-time failure, consider using SIL, which supports signal handlers and debugging.&lt;BR /&gt;&lt;BR /&gt;If you cannot find a solution, consider using the method setTimeoutRecvSecs of rtw.connectivity.RtIOStreamHostCommunicator to increase the timeout value.&lt;/SPAN&gt;&amp;nbsp;&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;Questions:&lt;BR /&gt;&amp;nbsp;&lt;BR /&gt;1. Does the S32K3x4EVB-T172 board require an external USB2Serial convertor for PIL or can it run PIL over the onboard OpenSDA port ?&amp;nbsp;&lt;BR /&gt;2. If an external USB2Serial convertor required , what is the exact hardware UART configuration expected?&amp;nbsp;&lt;BR /&gt;3. Am i missing any configuration ?&lt;BR /&gt;&lt;BR /&gt;Any guidance i highly appreciated!&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 31 Aug 2026 23:07:10 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Model-Based-Design-Toolbox-MBDT/S32K3x4EVB-T172-PIL-Communication-Error-Timeout-with-MBDT/m-p/2409795#M10811</guid>
      <dc:creator>PruthviB</dc:creator>
      <dc:date>2026-08-31T23:07:10Z</dc:date>
    </item>
    <item>
      <title>Re: S32K3x4EVB-T172 PIL Communication Error/ Timeout with MBDT S32K3xx 1.4.0</title>
      <link>https://community.nxp.com/t5/Model-Based-Design-Toolbox-MBDT/S32K3x4EVB-T172-PIL-Communication-Error-Timeout-with-MBDT/m-p/2409937#M10813</link>
      <description>&lt;P&gt;Hi,&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/265798"&gt;@PruthviB&lt;/a&gt;,&lt;/P&gt;
&lt;DIV&gt;
&lt;P&gt;Before investigating further, could you clarify why you are using &lt;STRONG&gt;MBDT S32K3xx v1.4.0&lt;/STRONG&gt;? The latest available release is &lt;STRONG&gt;v1.8.0&lt;/STRONG&gt;, which includes several fixes and improvements. We recommend upgrading to v1.8.0 first and checking whether the issue still reproduces.&lt;/P&gt;
&lt;P&gt;Regarding your setup, an &lt;STRONG&gt;external USB-to-Serial converter is not required for PIL communication&lt;/STRONG&gt; on the &lt;STRONG&gt;S32K3X4EVB-T172&lt;/STRONG&gt;. The onboard &lt;STRONG&gt;OpenSDA interface already provides access to the target UART used for host-target communication&lt;/STRONG&gt;, so the same USB connection can be used for both programming and PIL communication.&lt;/P&gt;
&lt;P&gt;Since OpenSDA has direct access to the UART pins, connecting an additional USB-to-Serial adapter is generally unnecessary and may even introduce configuration conflicts if multiple serial interfaces are active.&lt;/P&gt;
&lt;P&gt;Could you please try the example with:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;MBDT S32K3xx &lt;STRONG&gt;v1.8.0&lt;/STRONG&gt;&lt;/LI&gt;
&lt;LI&gt;Only the onboard &lt;STRONG&gt;OpenSDA USB connection&lt;/STRONG&gt;&lt;/LI&gt;
&lt;LI&gt;The COM port exposed by OpenSDA selected in the hardware settings&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Best regards,&lt;BR /&gt;Dragos&lt;/P&gt;
&lt;/DIV&gt;</description>
      <pubDate>Tue, 01 Sep 2026 07:47:33 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Model-Based-Design-Toolbox-MBDT/S32K3x4EVB-T172-PIL-Communication-Error-Timeout-with-MBDT/m-p/2409937#M10813</guid>
      <dc:creator>dragostoma</dc:creator>
      <dc:date>2026-09-01T07:47:33Z</dc:date>
    </item>
  </channel>
</rss>

