<?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>S110 Soft Device and wired UART</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/2004/s110-soft-device-and-wired-uart</link><description>I am using UART0 for wired communication and S110 for Bluetooth LE communication at the same time, using HRM profile. System seems to work as expected, I get log output from UART and heart rate is delivered via BTLE. However, after about three minutes</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 01 Apr 2014 09:37:12 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/2004/s110-soft-device-and-wired-uart" /><item><title>RE: S110 Soft Device and wired UART</title><link>https://devzone.nordicsemi.com/thread/8591?ContentTypeID=1</link><pubDate>Tue, 01 Apr 2014 09:37:12 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:2b22030b-ecad-4422-a585-787e89382a69</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;Jarmo, please have a look at buttons_init() function in main.c
An interrupt from the button (GPIOTE PORT interrupt) will wake the system up.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: S110 Soft Device and wired UART</title><link>https://devzone.nordicsemi.com/thread/8590?ContentTypeID=1</link><pubDate>Tue, 01 Apr 2014 07:58:33 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:0248ed07-34b0-4c93-8bea-11a655c1d672</guid><dc:creator>Jarmo</dc:creator><description>&lt;p&gt;Ok, that explains the thing, thanks for answer. What is the way to get the system wake up again?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: S110 Soft Device and wired UART</title><link>https://devzone.nordicsemi.com/thread/8589?ContentTypeID=1</link><pubDate>Mon, 31 Mar 2014 13:23:54 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ff0eb978-3666-4de4-acde-17913207591b</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;Jarmo, the HRM example will automatically enter deep sleep mode after advertising 3 minutes ( APP_ADV_TIMEOUT_IN_SECONDS)  without a connect request from a master.
You can wake the chip up by pressing a button on the board.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: S110 Soft Device and wired UART</title><link>https://devzone.nordicsemi.com/thread/8588?ContentTypeID=1</link><pubDate>Mon, 31 Mar 2014 10:28:12 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:2bd697d4-7a2e-46c1-b335-cc699c6573a9</guid><dc:creator>Jarmo</dc:creator><description>&lt;p&gt;Hi&lt;/p&gt;
&lt;p&gt;I just tried with pca10001\s110\ble_app_hrs stock example. It seems to work as long as I connect my Mac with LightBlue relatively soon after starting the ble_app_hrs. However, if I leave the example running without connecting (LightBlue not running on Mac), after a few minutes my Mac is no more able to find the Nordic_HRM profile or anything. Looks like the app has crashed or something, don&amp;#39;t know what.&lt;/p&gt;
&lt;p&gt;So I would say yes, similar issue is happening also with stock SDK example.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: S110 Soft Device and wired UART</title><link>https://devzone.nordicsemi.com/thread/8587?ContentTypeID=1</link><pubDate>Fri, 28 Mar 2014 15:28:58 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b722d346-c853-4363-84df-5680deb89ec1</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;Hi Jarmo,&lt;/p&gt;
&lt;p&gt;Stepping code line by line would not work if the stack is active, since the stack is not paused by the debugger.
What you should do is to add a breakpoint inside app_error_handler() to check if there is any assertion, and then look for the err_code, line number and file name of the function that cause the issue.&lt;/p&gt;
&lt;p&gt;Do you have the same issue with the stock SDK&amp;#39;s example ?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: S110 Soft Device and wired UART</title><link>https://devzone.nordicsemi.com/thread/8586?ContentTypeID=1</link><pubDate>Fri, 28 Mar 2014 14:45:46 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d7be3e12-0d52-45d4-a360-e4be73a94923</guid><dc:creator>Jarmo</dc:creator><description>&lt;p&gt;Now it looks like the problem is not UART related, because it happens also without that. System just runs bout three minutes and then crashes. I have to set up debugging environment and strip out code that actually causes the problem. However, I haven&amp;#39;t got uVision debugging working very well. Stepping code line by line does not work for me.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: S110 Soft Device and wired UART</title><link>https://devzone.nordicsemi.com/thread/8585?ContentTypeID=1</link><pubDate>Thu, 27 Mar 2014 16:07:38 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f9978625-8a5d-4dfd-8b3e-6514e99cbf0b</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;Hi Jarmo,&lt;/p&gt;
&lt;p&gt;Using simple_uart should not break the BLE link.&lt;/p&gt;
&lt;p&gt;I assume you are aware of the interrupt latency caused by BLE stack (CPU blocking time) that can affect the UART communication.&lt;/p&gt;
&lt;p&gt;Could you run on Debug mode and catch the BLE_GAP_EVT_DISCONNECTED event then look for the disconnect reason in ble_gap_evt_t ?&lt;/p&gt;
&lt;p&gt;If possible please send us your project for closer look.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>