<?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>BLE Multilink Central example not working on PCA10028</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/9649/ble-multilink-central-example-not-working-on-pca10028</link><description>Hi, 
 I am trying BLE multilink central example from SDK9 on PCA10028 board, but everytime device gets stuck at LEDS_CONFIGURE() in main.c. 
 Below is my setup: 
 
 Flash S120 softdevice via NRF Studio 
 goto nRF51_SDK_9.0.0_2e23562\examples\ble_central</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 12 Oct 2015 12:18:54 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/9649/ble-multilink-central-example-not-working-on-pca10028" /><item><title>RE: BLE Multilink Central example not working on PCA10028</title><link>https://devzone.nordicsemi.com/thread/35655?ContentTypeID=1</link><pubDate>Mon, 12 Oct 2015 12:18:54 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:44c2eb51-7881-4ee9-9659-1c67b5cf6e93</guid><dc:creator>Susheel Nuguru</dc:creator><description>&lt;p&gt;not sure what you mean by debug stuck in LEDS_CONFIGURE!!! LEDS_CONFIGURE is the first debuggable line in main.c so i guess the blue arrow is just stalled because the device went to sleep mode. If you put a breakpoint at other lines, you will see that they are executed normally.&lt;/p&gt;
&lt;p&gt;&lt;img src="https://devzone.nordicsemi.com/cfs-file/__key/communityserver-discussions-components-files/4/6013.Capture.PNG" alt="image description" /&gt;
When you run this application and hit stop, this blue pointer does not mean that the execution is still stuck there. It is not able to point to the correct place because the last execution was sd_app_event_wait() and then the chip went to sleep after executing the softdevice instructions.&lt;/p&gt;
&lt;p&gt;If you see the PC value, it points to inside the softdevice. Which is correct.
&lt;img src="https://devzone.nordicsemi.com/cfs-file/__key/communityserver-discussions-components-files/4/3480.Capture.PNG" alt="image description" /&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>