<?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>Acquired event doesn&amp;#39;t happen in NRF51822 as spi slave</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/7483/acquired-event-doesn-t-happen-in-nrf51822-as-spi-slave</link><description>Hey everyone.,
I was trying to use nrf51822 as spi slave and just a heads up to know that i use Nrf51822 as master. I see that when chip select CS gets low SPI needs to acquire semaphore in spi But when i was trying to debug. My program doesn&amp;#39;t hit NRF_ACQUIRE</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 16 Jun 2015 20:19:52 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/7483/acquired-event-doesn-t-happen-in-nrf51822-as-spi-slave" /><item><title>RE: Acquired event doesn't happen in NRF51822 as spi slave</title><link>https://devzone.nordicsemi.com/thread/26623?ContentTypeID=1</link><pubDate>Tue, 16 Jun 2015 20:19:52 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b094456d-5609-4802-9bf5-3e444ee0b259</guid><dc:creator>Susheel Nuguru</dc:creator><description>&lt;p&gt;Thanks for reporting your answer.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Acquired event doesn't happen in NRF51822 as spi slave</title><link>https://devzone.nordicsemi.com/thread/26622?ContentTypeID=1</link><pubDate>Fri, 12 Jun 2015 10:01:22 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:11a5cfed-6964-454f-b080-becf65a08121</guid><dc:creator>trk</dc:creator><description>&lt;p&gt;Hey everyone.
SpI in nrf51822 acquires semaphore when cs gets low and acquired event occurs when cpu gets semaphore.
Just a heads up to know., There is no spi slave in version 1 Nrf51822 dev kits. I used version 2 and that works.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Acquired event doesn't happen in NRF51822 as spi slave</title><link>https://devzone.nordicsemi.com/thread/26621?ContentTypeID=1</link><pubDate>Mon, 08 Jun 2015 20:28:32 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:a550a7c4-d8e5-42d1-9e7f-65dcd762a814</guid><dc:creator>Susheel Nuguru</dc:creator><description>&lt;p&gt;Give me some more information of whats your program was supposed to do and what it is doing. If you can post some code snippet then it would be easy to analyze. It is rather difficult to point out a problem described in this general way.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Acquired event doesn't happen in NRF51822 as spi slave</title><link>https://devzone.nordicsemi.com/thread/26620?ContentTypeID=1</link><pubDate>Mon, 08 Jun 2015 17:19:39 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:bb4dd9c5-e734-4e07-9b87-69357c227724</guid><dc:creator>trk</dc:creator><description>&lt;p&gt;I checked it. But my program does not go into loop at any point of the code.Thanks for reply tough @ARYAN&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Acquired event doesn't happen in NRF51822 as spi slave</title><link>https://devzone.nordicsemi.com/thread/26619?ContentTypeID=1</link><pubDate>Mon, 08 Jun 2015 16:56:06 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e0e9a8cd-7903-43d0-8c09-91582661e0c4</guid><dc:creator>Susheel Nuguru</dc:creator><description>&lt;p&gt;If you are already debugging, then try to find out where your program is stuck or looping. You can find that out in Keil by running your program for few seconds in debug mode and hitting the stop button. Keil will tell you the current line it was executing and you will find out the context.
Find out if there are any loops or wait states.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>