<?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>i.MX RT Crossover MCUsのトピックRe: LPSPI rxData = txData OK?</title>
    <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/LPSPI-rxData-txData-OK/m-p/1681424#M25818</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/181337"&gt;@p_shep&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Could you be more specific about your question? Which addresses are you refering to?&lt;/P&gt;
&lt;P&gt;Also can you please provide me the board you are using?&lt;/P&gt;
&lt;P&gt;Best Regards, Miguel.&lt;/P&gt;</description>
    <pubDate>Tue, 04 Jul 2023 18:31:54 GMT</pubDate>
    <dc:creator>Miguel04</dc:creator>
    <dc:date>2023-07-04T18:31:54Z</dc:date>
    <item>
      <title>LPSPI rxData == txData OK?</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/LPSPI-rxData-txData-OK/m-p/1681315#M25812</link>
      <description>&lt;P&gt;Assuming we don't care that the txData is overwritten, is it OK to set both addresses the same?&lt;/P&gt;&lt;P&gt;Is there any issue with the data getting corrupted?&lt;/P&gt;</description>
      <pubDate>Wed, 05 Jul 2023 07:45:59 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/LPSPI-rxData-txData-OK/m-p/1681315#M25812</guid>
      <dc:creator>p_shep</dc:creator>
      <dc:date>2023-07-05T07:45:59Z</dc:date>
    </item>
    <item>
      <title>Re: LPSPI rxData = txData OK?</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/LPSPI-rxData-txData-OK/m-p/1681424#M25818</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/181337"&gt;@p_shep&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Could you be more specific about your question? Which addresses are you refering to?&lt;/P&gt;
&lt;P&gt;Also can you please provide me the board you are using?&lt;/P&gt;
&lt;P&gt;Best Regards, Miguel.&lt;/P&gt;</description>
      <pubDate>Tue, 04 Jul 2023 18:31:54 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/LPSPI-rxData-txData-OK/m-p/1681424#M25818</guid>
      <dc:creator>Miguel04</dc:creator>
      <dc:date>2023-07-04T18:31:54Z</dc:date>
    </item>
    <item>
      <title>Re: LPSPI rxData = txData OK?</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/LPSPI-rxData-txData-OK/m-p/1681790#M25826</link>
      <description>&lt;P&gt;Address would be somewhere in D-TCM.&lt;/P&gt;&lt;P&gt;The board would be the IMXRT1064 EVK&lt;/P&gt;&lt;P&gt;I've been using it like this, but it looks like one or the other (out bound or inbound) data might be getting corrupted during transfer.&lt;/P&gt;&lt;P&gt;I would have thought that the tx data would be copied out of memory into the fifo, then on reception the rx data copied from the fifo into memory - so one, then the other - so would be ok.&lt;/P&gt;&lt;P&gt;That may not be the case!&lt;/P&gt;</description>
      <pubDate>Wed, 05 Jul 2023 07:44:47 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/LPSPI-rxData-txData-OK/m-p/1681790#M25826</guid>
      <dc:creator>p_shep</dc:creator>
      <dc:date>2023-07-05T07:44:47Z</dc:date>
    </item>
    <item>
      <title>Re: LPSPI rxData = txData OK?</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/LPSPI-rxData-txData-OK/m-p/1683453#M25862</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/181337"&gt;@p_shep&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;In our examples from the SDK there are 2 variables [masterRxData and masterTxData], if my understanding is correct is that you are trying to recieve and transmit using the same variable, it should not be the reason you are loosing data since the protocol uses the register to recieve and transmit.&lt;/P&gt;
&lt;P&gt;1. Are you developing your own driver or are you using the SDK?&lt;/P&gt;
&lt;P&gt;2. Have you tried using 2 variables [recieve and transmit]?&lt;/P&gt;
&lt;P&gt;3. How are you recieving and transmiting?&lt;/P&gt;
&lt;P&gt;Best Regards, Miguel.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 06 Jul 2023 20:58:35 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/LPSPI-rxData-txData-OK/m-p/1683453#M25862</guid>
      <dc:creator>Miguel04</dc:creator>
      <dc:date>2023-07-06T20:58:35Z</dc:date>
    </item>
    <item>
      <title>Re: LPSPI rxData = txData OK?</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/LPSPI-rxData-txData-OK/m-p/1683776#M25871</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;Thanks for help, that's good to know, can eliminate that a possibility.&lt;/P&gt;&lt;P&gt;Yep, using the standard SDK driver (2.2.0)&lt;/P&gt;</description>
      <pubDate>Fri, 07 Jul 2023 08:21:25 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/LPSPI-rxData-txData-OK/m-p/1683776#M25871</guid>
      <dc:creator>p_shep</dc:creator>
      <dc:date>2023-07-07T08:21:25Z</dc:date>
    </item>
  </channel>
</rss>

