<?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: LPC1768 SPI problem in LPC Microcontrollers</title>
    <link>https://community.nxp.com/t5/LPC-Microcontrollers/LPC1768-SPI-problem/m-p/520333#M3584</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;STRONG&gt;Content originally posted in LPCWare by LabRat on Mon Oct 20 01:56:29 MST 2014&lt;/STRONG&gt;&lt;BR /&gt;&lt;HR /&gt;&lt;SPAN style="color: #0000ff;"&gt;&lt;STRONG&gt;Quote: lc88&lt;/STRONG&gt;&lt;BR /&gt;For example the accelerometer needs at least 3 bytes per on communication cycle (i. e. period when chip select signal is active) while LPC's SPI module can send/receive no more than 16 bits of data in one transfer cycle.&lt;/SPAN&gt;&lt;HR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt; :quest: &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Then just send/receive 3 x 8 bits and switch CS like Tom shows it in this sample:&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;&lt;A class="jive-link-external-small" href="https://community.nxp.com/external-link.jspa?url=http%3A%2F%2Fdeveloper.mbed.org%2Fusers%2Ftkreyche%2Fnotebook%2Fadxl362_tkreyche%2F" rel="nofollow" target="_blank"&gt;http://developer.mbed.org/users/tkreyche/notebook/adxl362_tkreyche/&lt;/A&gt;&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 15 Jun 2016 17:44:02 GMT</pubDate>
    <dc:creator>lpcware</dc:creator>
    <dc:date>2016-06-15T17:44:02Z</dc:date>
    <item>
      <title>LPC1768 SPI problem</title>
      <link>https://community.nxp.com/t5/LPC-Microcontrollers/LPC1768-SPI-problem/m-p/520332#M3583</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;STRONG&gt;Content originally posted in LPCWare by lc88 on Mon Oct 20 01:16:54 MST 2014&lt;/STRONG&gt;&lt;BR /&gt;&lt;SPAN&gt; Hello,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;&lt;SPAN&gt; I have a Landtiger (&lt;/SPAN&gt;&lt;A class="jive-link-external-small" href="https://community.nxp.com/external-link.jspa?url=http%3A%2F%2Fdeveloper.mbed.org%2Fusers%2Fwim%2Fnotebook%2Flandtiger-baseboard%2F" rel="nofollow" target="_blank"&gt;http://developer.mbed.org/users/wim/notebook/landtiger-baseboard/&lt;/A&gt;&lt;SPAN&gt;) development board (I probably won't use its LCD display) with LPC1768 on it. My problem is that I need to communicate with ADXL362 accelerometer (Digilent pmodACL2) and L3G4200D (Digilent pmodGyro) via SPI. Is it possible to achieve it using hardware SPI (or SSP in SPI mode) embedded in LPC1768 chip ? I'm asking this question due to information enclosed in documentation of devices listed above. For example the accelerometer needs at least 3 bytes per on communication cycle (i. e. period when chip select signal is active) while LPC's SPI module can send/receive no more than 16 bits of data in one transfer cycle. I would also like to know whether LPC1768 could use its SPI hardware to work as master in multislave mode (I've got accelerometer and gyroscope)&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt; Please help me.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 15 Jun 2016 17:44:01 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPC-Microcontrollers/LPC1768-SPI-problem/m-p/520332#M3583</guid>
      <dc:creator>lpcware</dc:creator>
      <dc:date>2016-06-15T17:44:01Z</dc:date>
    </item>
    <item>
      <title>Re: LPC1768 SPI problem</title>
      <link>https://community.nxp.com/t5/LPC-Microcontrollers/LPC1768-SPI-problem/m-p/520333#M3584</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;STRONG&gt;Content originally posted in LPCWare by LabRat on Mon Oct 20 01:56:29 MST 2014&lt;/STRONG&gt;&lt;BR /&gt;&lt;HR /&gt;&lt;SPAN style="color: #0000ff;"&gt;&lt;STRONG&gt;Quote: lc88&lt;/STRONG&gt;&lt;BR /&gt;For example the accelerometer needs at least 3 bytes per on communication cycle (i. e. period when chip select signal is active) while LPC's SPI module can send/receive no more than 16 bits of data in one transfer cycle.&lt;/SPAN&gt;&lt;HR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt; :quest: &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Then just send/receive 3 x 8 bits and switch CS like Tom shows it in this sample:&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;&lt;A class="jive-link-external-small" href="https://community.nxp.com/external-link.jspa?url=http%3A%2F%2Fdeveloper.mbed.org%2Fusers%2Ftkreyche%2Fnotebook%2Fadxl362_tkreyche%2F" rel="nofollow" target="_blank"&gt;http://developer.mbed.org/users/tkreyche/notebook/adxl362_tkreyche/&lt;/A&gt;&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 15 Jun 2016 17:44:02 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPC-Microcontrollers/LPC1768-SPI-problem/m-p/520333#M3584</guid>
      <dc:creator>lpcware</dc:creator>
      <dc:date>2016-06-15T17:44:02Z</dc:date>
    </item>
    <item>
      <title>Re: LPC1768 SPI problem</title>
      <link>https://community.nxp.com/t5/LPC-Microcontrollers/LPC1768-SPI-problem/m-p/520334#M3585</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;STRONG&gt;Content originally posted in LPCWare by mazyarseyedi on Sun Mar 01 22:37:47 MST 2015&lt;/STRONG&gt;&lt;BR /&gt;&lt;SPAN&gt;if you go for micowire half -duplex you should be able to have a opcode of 8 bits and receive 16 bits&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;look at usermanual section 18.5.3 figures 82 and 83 &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;it seems you can have contiuos transfer (sending 8 bits and receiving 16 and repeating it)&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;also you may use only legacy spi&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 15 Jun 2016 17:44:02 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPC-Microcontrollers/LPC1768-SPI-problem/m-p/520334#M3585</guid>
      <dc:creator>lpcware</dc:creator>
      <dc:date>2016-06-15T17:44:02Z</dc:date>
    </item>
  </channel>
</rss>

