<?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: Unable to get a reading on data logging/scope on MBDT while in External Mode in Model-Based Design Toolbox (MBDT)</title>
    <link>https://community.nxp.com/t5/Model-Based-Design-Toolbox-MBDT/Unable-to-get-a-reading-on-data-logging-scope-on-MBDT-while-in/m-p/1675031#M8307</link>
    <description>&lt;P&gt;Hi, I found the solution to my issue: in Simulink's Hardware &lt;EM&gt;Settings&lt;/EM&gt; &amp;gt; &lt;EM&gt;External Mode&lt;/EM&gt; &amp;gt; &lt;EM&gt;Communication Interface&lt;/EM&gt;, I simply had to select "&lt;U&gt;&lt;STRONG&gt;&lt;EM&gt;XCP Serial Interface&lt;/EM&gt;&lt;/STRONG&gt;&lt;/U&gt;" instead of the "&lt;EM&gt;Serial Interface&lt;/EM&gt;" which was there by default. Now, I am able to log my data and see the "&lt;EM&gt;Data Inspector&lt;/EM&gt;" icon on the Simulink tab.&lt;/P&gt;&lt;P&gt;I still though have an issue when I close my Simulink model and re-open it, when I run it and it gets compiled and uploaded to board, I am hit with this error "&lt;EM&gt;External Mode Open Protocol Connect command failed Caused by: Could not connect to XCP slave: XCP Master internal error: Busy(0) or no timeout(2) for 255&lt;/EM&gt;" (which also happened when I used "&lt;EM&gt;Serial Interface&lt;/EM&gt;" although the error message was rephrased to "&lt;EM&gt;Error occurred while executing External Mode MEX-file 'ext_serial_win32_comm&lt;/EM&gt;"). My only solution is to always randomly change several Hardware Settings (baud rate, buffer, etc..), sample rate, comment out some blocks, and run it each time (which takes at least 1 hour of continuous fiddling), until it finally says "&lt;EM&gt;running on NXP MIMXRT1024..&lt;/EM&gt;", and I rejoice. And from there it will run every time as expected, until Simulink gets closed by mistake.&lt;/P&gt;</description>
    <pubDate>Fri, 23 Jun 2023 15:20:20 GMT</pubDate>
    <dc:creator>ylahdili</dc:creator>
    <dc:date>2023-06-23T15:20:20Z</dc:date>
    <item>
      <title>Unable to get a reading on data logging/scope on MBDT while in External Mode</title>
      <link>https://community.nxp.com/t5/Model-Based-Design-Toolbox-MBDT/Unable-to-get-a-reading-on-data-logging-scope-on-MBDT-while-in/m-p/1663458#M8264</link>
      <description>&lt;P&gt;We have a Simulink model that reads the ADC input of our &lt;STRONG&gt;i.MX RT1024&lt;/STRONG&gt; board, and displays it on a scope. To be able to visualize this input, we are running the model on &lt;STRONG&gt;External Mode&lt;/STRONG&gt; ("&lt;EM&gt;Tune &amp;amp; Monitor&lt;/EM&gt;" button). It successfully runs, and an LED correctly light up when potentiometer output (ADC input) exceeds a certain value. We are also able to press a virtual toggle button on the Simulink dashboard to turn the LED on and off.&lt;/P&gt;&lt;P&gt;But the problem is that we are unable to get the ADC input reading in Simulink: the scope connected to the output of ADC MBDT block is always blank. What can be the cause of this?&lt;/P&gt;&lt;P&gt;Thank you very much.&lt;/P&gt;</description>
      <pubDate>Mon, 05 Jun 2023 11:54:23 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Model-Based-Design-Toolbox-MBDT/Unable-to-get-a-reading-on-data-logging-scope-on-MBDT-while-in/m-p/1663458#M8264</guid>
      <dc:creator>ylahdili</dc:creator>
      <dc:date>2023-06-05T11:54:23Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to get a reading on data logging/scope on MBDT while in External Mode</title>
      <link>https://community.nxp.com/t5/Model-Based-Design-Toolbox-MBDT/Unable-to-get-a-reading-on-data-logging-scope-on-MBDT-while-in/m-p/1675031#M8307</link>
      <description>&lt;P&gt;Hi, I found the solution to my issue: in Simulink's Hardware &lt;EM&gt;Settings&lt;/EM&gt; &amp;gt; &lt;EM&gt;External Mode&lt;/EM&gt; &amp;gt; &lt;EM&gt;Communication Interface&lt;/EM&gt;, I simply had to select "&lt;U&gt;&lt;STRONG&gt;&lt;EM&gt;XCP Serial Interface&lt;/EM&gt;&lt;/STRONG&gt;&lt;/U&gt;" instead of the "&lt;EM&gt;Serial Interface&lt;/EM&gt;" which was there by default. Now, I am able to log my data and see the "&lt;EM&gt;Data Inspector&lt;/EM&gt;" icon on the Simulink tab.&lt;/P&gt;&lt;P&gt;I still though have an issue when I close my Simulink model and re-open it, when I run it and it gets compiled and uploaded to board, I am hit with this error "&lt;EM&gt;External Mode Open Protocol Connect command failed Caused by: Could not connect to XCP slave: XCP Master internal error: Busy(0) or no timeout(2) for 255&lt;/EM&gt;" (which also happened when I used "&lt;EM&gt;Serial Interface&lt;/EM&gt;" although the error message was rephrased to "&lt;EM&gt;Error occurred while executing External Mode MEX-file 'ext_serial_win32_comm&lt;/EM&gt;"). My only solution is to always randomly change several Hardware Settings (baud rate, buffer, etc..), sample rate, comment out some blocks, and run it each time (which takes at least 1 hour of continuous fiddling), until it finally says "&lt;EM&gt;running on NXP MIMXRT1024..&lt;/EM&gt;", and I rejoice. And from there it will run every time as expected, until Simulink gets closed by mistake.&lt;/P&gt;</description>
      <pubDate>Fri, 23 Jun 2023 15:20:20 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Model-Based-Design-Toolbox-MBDT/Unable-to-get-a-reading-on-data-logging-scope-on-MBDT-while-in/m-p/1675031#M8307</guid>
      <dc:creator>ylahdili</dc:creator>
      <dc:date>2023-06-23T15:20:20Z</dc:date>
    </item>
  </channel>
</rss>

