<?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>NRF_LOG no debug log in SEGGER for BLE_SDK 12.3</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/27129/nrf_log-no-debug-log-in-segger-for-ble_sdk-12-3</link><description>I am using SEGGER Studio on MacOSx. 
 When use the latest mesh SDK, I can run the light_control example and see the debug log in the Debug Terminal of SEGGER Studio. 
 However, when I use BLE SDK 12.3, I simply cannot see the logs for ble_app_hrs. </description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 17 Nov 2017 20:11:58 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/27129/nrf_log-no-debug-log-in-segger-for-ble_sdk-12-3" /><item><title>RE: NRF_LOG no debug log in SEGGER for BLE_SDK 12.3</title><link>https://devzone.nordicsemi.com/thread/106788?ContentTypeID=1</link><pubDate>Fri, 17 Nov 2017 20:11:58 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:c6226972-736d-417c-85cd-27211fd424fa</guid><dc:creator>kevinong</dc:creator><description>&lt;p&gt;I have the same problem, but I found the root cause!
You should to check &amp;quot;Debugged device&amp;quot;, maybe you choose wrong MCU.&lt;/p&gt;
&lt;p&gt;For my case, target board use nRF51822_xxAC, but &amp;quot;Debugged device&amp;quot; choose nRF51822_xxAA. The RAM size is different, RTT only load 16KB for xxAA, not 32KB for xxAC.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: NRF_LOG no debug log in SEGGER for BLE_SDK 12.3</title><link>https://devzone.nordicsemi.com/thread/106786?ContentTypeID=1</link><pubDate>Thu, 24 Aug 2017 14:02:34 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:a240b84d-ddb7-4219-80a4-4beaa3910e4a</guid><dc:creator>Sigurd</dc:creator><description>&lt;p&gt;Are you getting the &amp;quot;Heart Rate Sensor example started.&amp;quot; message in the built-in terminal in SES ?&lt;/p&gt;
&lt;p&gt;Do you see this message if you use J-Link RTT viewer program?&lt;/p&gt;
&lt;p&gt;If not, does it help to set &lt;code&gt;NRF_LOG_DEFERRED&lt;/code&gt; to 0 in &lt;code&gt;sdk_config.h&lt;/code&gt; ?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: NRF_LOG no debug log in SEGGER for BLE_SDK 12.3</title><link>https://devzone.nordicsemi.com/thread/106789?ContentTypeID=1</link><pubDate>Tue, 22 Aug 2017 14:21:06 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e6f299c2-279b-4c92-a8ae-7cde5ddbfc36</guid><dc:creator>zed</dc:creator><description>&lt;p&gt;Yup I just downloaded the SDK again and followed all the steps (which I didn&amp;#39;t follow before, I just got it to work through reading multiple questions). The debug log is still empty, but the application is running fine.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: NRF_LOG no debug log in SEGGER for BLE_SDK 12.3</title><link>https://devzone.nordicsemi.com/thread/106787?ContentTypeID=1</link><pubDate>Mon, 21 Aug 2017 07:55:25 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d9376f0c-89ea-4d04-bedf-0ad014ed9f1d</guid><dc:creator>Sigurd</dc:creator><description>&lt;p&gt;Did you get it to work after following the guide?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: NRF_LOG no debug log in SEGGER for BLE_SDK 12.3</title><link>https://devzone.nordicsemi.com/thread/106793?ContentTypeID=1</link><pubDate>Fri, 18 Aug 2017 15:04:53 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b13e529b-ffb4-4291-82e9-ed1a35602032</guid><dc:creator>zed</dc:creator><description>&lt;p&gt;v3.25, tried also with 3.24. I&amp;#39;m importing from IAR. I&amp;#39;ll try to setup that again. Note that the debug break points work, it is just the log that doesn&amp;#39;t show.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: NRF_LOG no debug log in SEGGER for BLE_SDK 12.3</title><link>https://devzone.nordicsemi.com/thread/106792?ContentTypeID=1</link><pubDate>Fri, 18 Aug 2017 15:00:42 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:cbf54f5b-1d5c-4eeb-bd52-1d13ea187b2a</guid><dc:creator>Sigurd</dc:creator><description>&lt;p&gt;What version of Segger Embedded Studio are you using? Could be some issue with your project file maybe. Did you follow &lt;a href="https://devzone.nordicsemi.com/blogs/1032/segger-embedded-studio-a-cross-platform-ide/"&gt;this guide&lt;/a&gt; for converting the Keil ble_app_hrs project file into a Segger Embedded Studio project ?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: NRF_LOG no debug log in SEGGER for BLE_SDK 12.3</title><link>https://devzone.nordicsemi.com/thread/106795?ContentTypeID=1</link><pubDate>Fri, 18 Aug 2017 13:33:43 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:0eaa59f7-3054-4c13-9ddc-48ae25c16030</guid><dc:creator>zed</dc:creator><description>&lt;p&gt;I build the project, download the new hex, then connect JLINK, attach debugger, Debug -&amp;gt; Go. The same steps work for mesh-sdk.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: NRF_LOG no debug log in SEGGER for BLE_SDK 12.3</title><link>https://devzone.nordicsemi.com/thread/106794?ContentTypeID=1</link><pubDate>Fri, 18 Aug 2017 13:29:01 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:c8528fea-7255-4082-be89-36849c38715f</guid><dc:creator>Sigurd</dc:creator><description>&lt;p&gt;Just to make sure... you have started the program by selecting Debug -&amp;gt; Build and Run, and after that pressed the green play button ?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: NRF_LOG no debug log in SEGGER for BLE_SDK 12.3</title><link>https://devzone.nordicsemi.com/thread/106791?ContentTypeID=1</link><pubDate>Fri, 18 Aug 2017 13:09:47 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:7bf22498-da4a-455a-b2a0-a902fcc9db47</guid><dc:creator>zed</dc:creator><description>&lt;p&gt;Yes it works fine. The LED blinks and I can connect to it using my phone. I used both UART and RTT, neither of them show debug log in Segger IDE / RttViewer in terminal.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: NRF_LOG no debug log in SEGGER for BLE_SDK 12.3</title><link>https://devzone.nordicsemi.com/thread/106790?ContentTypeID=1</link><pubDate>Fri, 18 Aug 2017 13:08:10 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d3c52e1f-120b-4f87-b777-2a62a162bf8b</guid><dc:creator>Sigurd</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;You always need to init the log module before you print something with NRF_LOG_INFO().&lt;/p&gt;
&lt;p&gt;Does the application work as expected(i.e. LED 1 is blinking, and you are able to connect with your phone)?&lt;/p&gt;
&lt;p&gt;It works fine here with&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;NRF_LOG_ENABLED 1
NRF_LOG_BACKEND_SERIAL_USES_UART 0
NRF_LOG_BACKEND_SERIAL_USES_RTT 1
&lt;/code&gt;&lt;/pre&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>