<?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>Model-Based Design Toolbox (MBDT)のトピックRe: Configuring DSPI with MPC5643xL toolbox</title>
    <link>https://community.nxp.com/t5/Model-Based-Design-Toolbox-MBDT/Configuring-DSPI-with-MPC5643xL-toolbox/m-p/620662#M75</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi &lt;A _jive_internal="true" data-content-finding="Community" data-userid="264088" data-username="yuchenchen" href="https://community.nxp.com/people/yuchenchen"&gt;&lt;SPAN style="color: #0066cc; text-decoration: underline;"&gt;Yuchen CHEN&lt;/SPAN&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Conceptual - your model is correct, it contains all the blocks you need and all the settings.&lt;/P&gt;&lt;P&gt;First, i would try to double check if the DSPI transmit works as expected and the mesage is received corectly by hall sensors. Perhasp you own an oscilloscope to verify this.&lt;/P&gt;&lt;P&gt;If transmit does not work, then you might need to tweek the DSPI config block: try different settings for Transfer Mode especially for delays.&lt;/P&gt;&lt;P&gt;If the trasmit is ok, then you would need to focus on receive path. The first thing i would do it to increment a variable in the Function-Call Subsystem that is supposed to be triggered when a msg is received.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps!&lt;/P&gt;&lt;P&gt;Daniel&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 20 Feb 2017 12:19:48 GMT</pubDate>
    <dc:creator>Daniel_Popa</dc:creator>
    <dc:date>2017-02-20T12:19:48Z</dc:date>
    <item>
      <title>Configuring DSPI with MPC5643xL toolbox</title>
      <link>https://community.nxp.com/t5/Model-Based-Design-Toolbox-MBDT/Configuring-DSPI-with-MPC5643xL-toolbox/m-p/620661#M74</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I'm configuring the DSPI port to read the data from a hall sensor through SPI. For the sensor itself, I need to send out a write command through MOSI and then read the data back through MISO. Attached&amp;nbsp;is my model.&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have talked to the halls sensor supplier technical support and confirm that 0xFFFF is the right signal I should send out as a read command, but I'm still not reading the proper data back. The read message is always a constant however I turn the shaft whose angle I'm trying to measure. Can anyone please help me take a look at the model? Is it doing the correct thing I'm expecting it to do?&lt;/P&gt;&lt;P&gt;Thank you so much!&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Original Attachment has been moved to: &lt;A _jive_internal="true" href="https://community.nxp.com/docs/DOC-339123"&gt;dspi_2015a.slx.zip&lt;/A&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 09 Feb 2017 23:00:02 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Model-Based-Design-Toolbox-MBDT/Configuring-DSPI-with-MPC5643xL-toolbox/m-p/620661#M74</guid>
      <dc:creator>yuchenchen</dc:creator>
      <dc:date>2017-02-09T23:00:02Z</dc:date>
    </item>
    <item>
      <title>Re: Configuring DSPI with MPC5643xL toolbox</title>
      <link>https://community.nxp.com/t5/Model-Based-Design-Toolbox-MBDT/Configuring-DSPI-with-MPC5643xL-toolbox/m-p/620662#M75</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi &lt;A _jive_internal="true" data-content-finding="Community" data-userid="264088" data-username="yuchenchen" href="https://community.nxp.com/people/yuchenchen"&gt;&lt;SPAN style="color: #0066cc; text-decoration: underline;"&gt;Yuchen CHEN&lt;/SPAN&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Conceptual - your model is correct, it contains all the blocks you need and all the settings.&lt;/P&gt;&lt;P&gt;First, i would try to double check if the DSPI transmit works as expected and the mesage is received corectly by hall sensors. Perhasp you own an oscilloscope to verify this.&lt;/P&gt;&lt;P&gt;If transmit does not work, then you might need to tweek the DSPI config block: try different settings for Transfer Mode especially for delays.&lt;/P&gt;&lt;P&gt;If the trasmit is ok, then you would need to focus on receive path. The first thing i would do it to increment a variable in the Function-Call Subsystem that is supposed to be triggered when a msg is received.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps!&lt;/P&gt;&lt;P&gt;Daniel&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 20 Feb 2017 12:19:48 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Model-Based-Design-Toolbox-MBDT/Configuring-DSPI-with-MPC5643xL-toolbox/m-p/620662#M75</guid>
      <dc:creator>Daniel_Popa</dc:creator>
      <dc:date>2017-02-20T12:19:48Z</dc:date>
    </item>
    <item>
      <title>Re: Configuring DSPI with MPC5643xL toolbox</title>
      <link>https://community.nxp.com/t5/Model-Based-Design-Toolbox-MBDT/Configuring-DSPI-with-MPC5643xL-toolbox/m-p/620663#M76</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I figured the out earlier. It turned out to be a shorted chip select pin.&amp;nbsp;&lt;/P&gt;&lt;P&gt;I reconfigured another chip select pin from a resolver module on the board and it worked, I was able to read success transmission from my SPI monitor.&lt;/P&gt;&lt;P&gt;The sensor didn't send the data back though. Then I found the duration of each message read by the SPI monitor is 1.74 micro&amp;nbsp;seconds. I changed the scalars and prescalars to slow it down and fixed the issue. The sensor is not capable of read data of so high speed I'm guessing.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 21 Feb 2017 21:14:42 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Model-Based-Design-Toolbox-MBDT/Configuring-DSPI-with-MPC5643xL-toolbox/m-p/620663#M76</guid>
      <dc:creator>yuchenchen</dc:creator>
      <dc:date>2017-02-21T21:14:42Z</dc:date>
    </item>
    <item>
      <title>Re: Configuring DSPI with MPC5643xL toolbox</title>
      <link>https://community.nxp.com/t5/Model-Based-Design-Toolbox-MBDT/Configuring-DSPI-with-MPC5643xL-toolbox/m-p/620664#M77</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Well done &lt;SPAN&gt;&lt;STRONG&gt;Yuchen CHEN&lt;/STRONG&gt; !&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Thank you for sharing your findings with us. &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Please consider posting your latest model + resolver module type here if you have the posibility and clearance.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;In case others will need a similar solution they can use your trademark design as a reference.&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 22 Feb 2017 06:25:41 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Model-Based-Design-Toolbox-MBDT/Configuring-DSPI-with-MPC5643xL-toolbox/m-p/620664#M77</guid>
      <dc:creator>Daniel_Popa</dc:creator>
      <dc:date>2017-02-22T06:25:41Z</dc:date>
    </item>
  </channel>
</rss>

