<?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>LPCXpresso IDEのトピックRe: SPI - full duplex communication</title>
    <link>https://community.nxp.com/t5/LPCXpresso-IDE/SPI-full-duplex-communication/m-p/554460#M13239</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;STRONG&gt;Content originally posted in LPCWare by ECamino on Thu Aug 15 07:52:07 MST 2013&lt;/STRONG&gt;&lt;BR /&gt;&lt;SPAN&gt;Hi,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;If there is data ready for tx on MISO, then the clock signal makes the slave send it out to the master making the com full duplex.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;In your main loop, why not create a function that will read the appropriate registers (not sure, but my guess would be TX/RTRIS or TX/RTMIS?) to see if there is data tx/rx ready?&amp;nbsp; If so, you can set a flag or change a state, return and continue.&amp;nbsp; This way you poll the SPI (no interrupts) and be non-blocking.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Have you searched for example code from LPCware or LPCXpresso?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;EC&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 15 Jun 2016 23:30:27 GMT</pubDate>
    <dc:creator>lpcware</dc:creator>
    <dc:date>2016-06-15T23:30:27Z</dc:date>
    <item>
      <title>SPI - full duplex communication</title>
      <link>https://community.nxp.com/t5/LPCXpresso-IDE/SPI-full-duplex-communication/m-p/554459#M13238</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;STRONG&gt;Content originally posted in LPCWare by tyassin on Thu Aug 15 06:19:03 MST 2013&lt;/STRONG&gt;&lt;BR /&gt;&lt;SPAN&gt;Hello,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I have a quetion on how the SPI work when there is communication between two LPC's.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;I have a setup where two MCUs are connected together(LPC1114) whith MOSI-MOSI, MISO-MISO, CLK-CLK and SSEL-SSEL connected together. If I do not want to use interrupts how or when does the slave pick up the data?&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Do you make a while loop where it waits until SSEL is toggled low or how????&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Another question is regarding the flow of the data. IS it correct when the master toggle SSEL that both the master and the slave can write to its respectively DR-register or is there a certain sequence this has to happen?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I have read the datasheet several times but am really not sure about these things. So will appriciate it a lot if someone could explain.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Thank you.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Regards. &lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 15 Jun 2016 23:30:26 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPCXpresso-IDE/SPI-full-duplex-communication/m-p/554459#M13238</guid>
      <dc:creator>lpcware</dc:creator>
      <dc:date>2016-06-15T23:30:26Z</dc:date>
    </item>
    <item>
      <title>Re: SPI - full duplex communication</title>
      <link>https://community.nxp.com/t5/LPCXpresso-IDE/SPI-full-duplex-communication/m-p/554460#M13239</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;STRONG&gt;Content originally posted in LPCWare by ECamino on Thu Aug 15 07:52:07 MST 2013&lt;/STRONG&gt;&lt;BR /&gt;&lt;SPAN&gt;Hi,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;If there is data ready for tx on MISO, then the clock signal makes the slave send it out to the master making the com full duplex.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;In your main loop, why not create a function that will read the appropriate registers (not sure, but my guess would be TX/RTRIS or TX/RTMIS?) to see if there is data tx/rx ready?&amp;nbsp; If so, you can set a flag or change a state, return and continue.&amp;nbsp; This way you poll the SPI (no interrupts) and be non-blocking.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Have you searched for example code from LPCware or LPCXpresso?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;EC&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 15 Jun 2016 23:30:27 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPCXpresso-IDE/SPI-full-duplex-communication/m-p/554460#M13239</guid>
      <dc:creator>lpcware</dc:creator>
      <dc:date>2016-06-15T23:30:27Z</dc:date>
    </item>
    <item>
      <title>Re: SPI - full duplex communication</title>
      <link>https://community.nxp.com/t5/LPCXpresso-IDE/SPI-full-duplex-communication/m-p/554461#M13240</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;STRONG&gt;Content originally posted in LPCWare by tyassin on Thu Aug 15 12:09:30 MST 2013&lt;/STRONG&gt;&lt;BR /&gt;&lt;SPAN&gt;Hi&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Ok I see. So in principle the slave can write a single byte to its data register and then do something else and when the master then starts to communicate, this data will be send to the master?&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;You are right there are a status register which indicate if the FIFO is full or not full or whether the SPI is idle or sending/receiving a frame. I guess it is this register you refer to.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;There are examples which I have looked at, but I am not completely sure how they operate.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Thank you for your reply&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 15 Jun 2016 23:30:27 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPCXpresso-IDE/SPI-full-duplex-communication/m-p/554461#M13240</guid>
      <dc:creator>lpcware</dc:creator>
      <dc:date>2016-06-15T23:30:27Z</dc:date>
    </item>
  </channel>
</rss>

