<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://devzone.nordicsemi.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>nrf52dk MBED SPI problem</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/37251/nrf52dk-mbed-spi-problem</link><description>Hi, 
 I have a problem with nrf52dk SPI with the mbed compiler. In the mbed pin names file for nrf52dk the pins are p22,p23,p24,p25. I connect many spi sensors and not working. 
 
 This is how I configure the spi 
 SPI spi(SPIS_PSELMOSI, SPIS_PSELMISO</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 08 Aug 2018 12:45:41 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/37251/nrf52dk-mbed-spi-problem" /><item><title>RE: nrf52dk MBED SPI problem</title><link>https://devzone.nordicsemi.com/thread/143372?ContentTypeID=1</link><pubDate>Wed, 08 Aug 2018 12:45:41 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:15c5a226-a3ff-432b-a0c5-4aef2e67d755</guid><dc:creator>Martin Lesund</dc:creator><description>&lt;p&gt;Hi Hk,&lt;/p&gt;
&lt;p&gt;A little more information would be helpful. &lt;em&gt;What does not work? What happens?&amp;nbsp;&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Have you connected to the correct pins? ++&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;I am not familiar with the &amp;quot;mbed compiler&amp;quot;, I would suggest that you post mbed questions on &lt;a href="https://os.mbed.com/questions/related/72/157/Nordic-nRF52-DK/" target="_blank" rel="noopener noreferrer"&gt;their&amp;nbsp;forum&lt;/a&gt;&amp;nbsp;if you want to use that.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;I would rather recommend that you use our &lt;a href="http://infocenter.nordicsemi.com/index.jsp?topic=%2Fcom.nordic.infocenter.sdk5.v15.0.0%2Findex.html&amp;amp;cp=4_0_0" target="_blank" rel="noopener noreferrer"&gt;SDK&lt;/a&gt; which already has a &lt;a href="http://infocenter.nordicsemi.com/index.jsp?topic=%2Fcom.nordic.infocenter.sdk5.v15.0.0%2Fspi_master_example.html&amp;amp;cp=4_0_0_4_5_36" target="_blank" rel="noopener noreferrer"&gt;SPI master application example&lt;/a&gt;&amp;nbsp;which you can use.&lt;/p&gt;
&lt;p&gt;You can use &lt;a href="http://infocenter.nordicsemi.com/index.jsp?topic=%2Fcom.nordic.infocenter.gs.ses%2Fdita%2Fgs%2Fdeveloping%2Fintro.html" target="_blank" rel="noopener noreferrer"&gt;SES IDE&amp;nbsp;&lt;/a&gt;(free) for development.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Anyway, when working with SPI I would highly recommend that you connect the signals to a logic analyser (ex. &lt;a href="https://www.saleae.com/"&gt;this&lt;/a&gt;) to actually see what is happening with the communication.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>