<?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>An issue in NRF51822 custom board as spi slave with BLE</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/62835/an-issue-in-nrf51822-custom-board-as-spi-slave-with-ble</link><description>Hello there, 
 
 I&amp;#39;m trying to use my NRF51822 custom board as spi slave with BLE that sending whatever received from the master. I&amp;#39;m using MSP430FR5994 as the master. 
 I&amp;#39;m using 110 softdevice and SDK v10. I tried to combine both BLE peripheral and</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 02 Jul 2020 14:08:44 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/62835/an-issue-in-nrf51822-custom-board-as-spi-slave-with-ble" /><item><title>RE: An issue in NRF51822 custom board as spi slave with BLE</title><link>https://devzone.nordicsemi.com/thread/258144?ContentTypeID=1</link><pubDate>Thu, 02 Jul 2020 14:08:44 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:9bf67cc3-5db2-4d1c-ad82-76365c1955f7</guid><dc:creator>aalsubhi</dc:creator><description>&lt;p&gt;Thanks, Turbo for your help. It turned out to be a power issue with My PCB.&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: An issue in NRF51822 custom board as spi slave with BLE</title><link>https://devzone.nordicsemi.com/thread/256052?ContentTypeID=1</link><pubDate>Sun, 21 Jun 2020 06:36:57 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:9c462fac-d098-49ba-81fb-797d8ea8072f</guid><dc:creator>Turbo J</dc:creator><description>&lt;p&gt;Irrelevant: SPIS does not rely on pin changing interrupts - it uses the CS signal directly in hardware.&lt;/p&gt;
&lt;p&gt;The only effect here would be a delay between end-of-transaction and the actual SPIS interrupt handler being executed.&lt;/p&gt;
&lt;p&gt;At this point I recommend cutting the CS wire/trace and putting a series resistor (100R - 1k) in. This lets you &lt;em&gt;measure&lt;/em&gt; which chip powers the line with a multimeter. Oscilloscope would be nice, too...&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: An issue in NRF51822 custom board as spi slave with BLE</title><link>https://devzone.nordicsemi.com/thread/256047?ContentTypeID=1</link><pubDate>Sat, 20 Jun 2020 22:26:32 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:7f4ea264-0610-47f4-b93a-b36a80fa2a35</guid><dc:creator>aalsubhi</dc:creator><description>&lt;p&gt;I found this in the SDK v10 documentation about GPIOs which might explain why CS pin never goes low:&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;h2&gt;Working with a SoftDevice&lt;/h2&gt;
&lt;p&gt;When a SoftDevice is enabled, it can interrupt the application at any time for a certain amount of time. T&lt;strong&gt;his can lead to &lt;/strong&gt;the situation&lt;strong&gt; where some pin level changes are missed&lt;/strong&gt;. If the application must track an input pin that can change its level frequently, PPI should be used with a high-accuracy event together with a TIMER in counter mode to count the detected transitions.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Any idea/example of how to do what is suggested?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: An issue in NRF51822 custom board as spi slave with BLE</title><link>https://devzone.nordicsemi.com/thread/256044?ContentTypeID=1</link><pubDate>Sat, 20 Jun 2020 20:34:29 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:49d5ef19-9e04-48c8-8e69-983cb5b95f78</guid><dc:creator>aalsubhi</dc:creator><description>&lt;p&gt;Also, I used the SEGGER RTT library to print out the error code for &amp;quot;nrf_drv_spis_init&amp;quot; and it was returning &amp;nbsp;0 which means the spis&amp;nbsp;initiated successfully.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: An issue in NRF51822 custom board as spi slave with BLE</title><link>https://devzone.nordicsemi.com/thread/256042?ContentTypeID=1</link><pubDate>Sat, 20 Jun 2020 16:54:56 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:6a68c8a3-621a-48ec-8242-78d9ee944f71</guid><dc:creator>aalsubhi</dc:creator><description>&lt;p&gt;I&amp;#39;m not using uart at all in my code or including any&amp;nbsp;uart driver/ code. Also, I tested the connectivity of the CS pin by using the continuity&amp;nbsp;test on a multimeter. I placed one prob on NRF51822 CS pin and the other prob on MSP40 (master) pin where is&amp;nbsp;&lt;span&gt;NRF51822 CS is connected. The connection is fine.&amp;nbsp;&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: An issue in NRF51822 custom board as spi slave with BLE</title><link>https://devzone.nordicsemi.com/thread/256036?ContentTypeID=1</link><pubDate>Sat, 20 Jun 2020 14:59:01 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:569158be-fdaf-4339-9389-3457206ca65d</guid><dc:creator>Turbo J</dc:creator><description>[quote userid="91350" url="~/f/nordic-q-a/62835/an-issue-in-nrf51822-custom-board-as-spi-slave-with-ble"]hen I connected &lt;span&gt;the NRF51822 custom board, the CS never goes low ( it always high even when the Master drives it low to start the spi&amp;nbsp;communication&amp;nbsp;).&amp;nbsp;&lt;/span&gt;[/quote]
&lt;p&gt;That could only happen if it is either not properly connected or the pin is configured elsewhere as an output (e.g. for UART).&lt;/p&gt;
&lt;p&gt;If two outputs fight each other, the resulting voltage is usually somewhere &amp;quot;in the middle&amp;quot; - but if the pin is in high drive mode there might be a chance it overwhelms the MSP IO pin.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>