<?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>Thingy52 Costume Firmware - Logging Module Issue - Lagging BLE Notificatio</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/42895/thingy52-costume-firmware---logging-module-issue---lagging-ble-notificatio</link><description>Hello Dev-Community, I have modified the Thingy Firmware for a custom made board which has also the MPU9250 with TWI connected. Everything works fine, if i use RTT Viewer. But when i don&amp;#39;t show the log, the ble service notification doesn&amp;#39;t send any notification</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 04 Feb 2019 10:30:08 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/42895/thingy52-costume-firmware---logging-module-issue---lagging-ble-notificatio" /><item><title>RE: Thingy52 Costume Firmware - Logging Module Issue - Lagging BLE Notificatio</title><link>https://devzone.nordicsemi.com/thread/169271?ContentTypeID=1</link><pubDate>Mon, 04 Feb 2019 10:30:08 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:38870f86-b838-4075-924c-1e8656a62ae1</guid><dc:creator>Susheel Nuguru</dc:creator><description>&lt;p&gt;it needs some investigation to understand why sleep is causing overflows. I am suspecting wrong configuration of some log macros in sdk_config.h file.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Thingy52 Costume Firmware - Logging Module Issue - Lagging BLE Notificatio</title><link>https://devzone.nordicsemi.com/thread/169270?ContentTypeID=1</link><pubDate>Mon, 04 Feb 2019 10:30:08 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:7d32c810-2200-4bb7-9ae7-3686f6ac5cf2</guid><dc:creator>Susheel Nuguru</dc:creator><description>&lt;p&gt;it needs some investigation to understand why sleep is causing overflows. I am suspecting wrong configuration of some log macros in sdk_config.h file.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Thingy52 Costume Firmware - Logging Module Issue - Lagging BLE Notificatio</title><link>https://devzone.nordicsemi.com/thread/169206?ContentTypeID=1</link><pubDate>Mon, 04 Feb 2019 05:48:48 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:6f89bb93-cc92-44c7-80d1-8936b10fd71b</guid><dc:creator>DominikP93</dc:creator><description>&lt;p&gt;Thank you so much. If i comment out the sleep function (sd_app_evt_wait), it works. But this means the chip will consume more power because between events he will not be in sleep mode, right?. In the original code of the thingy it works with the sleep mode function. Why doesn&amp;#39;t it work in my code?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Thingy52 Costume Firmware - Logging Module Issue - Lagging BLE Notificatio</title><link>https://devzone.nordicsemi.com/thread/167865?ContentTypeID=1</link><pubDate>Fri, 25 Jan 2019 10:35:02 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:200d7ca3-2e90-4236-a2b1-0fea2aef469d</guid><dc:creator>Susheel Nuguru</dc:creator><description>[quote user="DominikP93"] As soon as i connect my RTT Viewer to the NRF52 the TMS Service works perfectly[/quote]
&lt;p&gt;&amp;nbsp;This seems like a bug somewhere. Can you try something, can you please comment out the sleep functions in the code (sd_app_evt_wait) throughout your code and see if there is any difference. This is to rule out something I saw on one chip and want to rule out certain possibilities.&lt;/p&gt;
&lt;p&gt;If commenting out sd_app_evt_wait still has the same behavior and your code does not work without debugger connected, then I need to reproduce it here at my desk. It could either be a timing issue in your code.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Thingy52 Costume Firmware - Logging Module Issue - Lagging BLE Notificatio</title><link>https://devzone.nordicsemi.com/thread/167797?ContentTypeID=1</link><pubDate>Fri, 25 Jan 2019 04:52:08 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:c00f5e6c-e9fe-4246-9074-2bf058689953</guid><dc:creator>DominikP93</dc:creator><description>&lt;p&gt;Thank you for the response. Since Thingy is running with SDK 13. There is no NRF_LOG_ALLOW_OVERFLOW. And also i disabled the logging module (and tried everything else) and still the same thing happends. As soon as i connect my RTT Viewer to the NRF52 the TMS Service works perfectly. But when i let it run by itself, its not sending anything or rarely something.&lt;br /&gt;&lt;br /&gt;What happenes when i connect RTT Viewer? Maybe it has something to do with the Segger RTT files?&amp;nbsp;&lt;br /&gt;&lt;br /&gt;I would appreciate again your help.&lt;br /&gt;&lt;br /&gt;Thanks,&lt;br /&gt;Dominik Pflumm&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Thingy52 Costume Firmware - Logging Module Issue - Lagging BLE Notificatio</title><link>https://devzone.nordicsemi.com/thread/167566?ContentTypeID=1</link><pubDate>Thu, 24 Jan 2019 09:11:06 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:c891f8c6-ec79-4bf5-8eb8-3e85065ee007</guid><dc:creator>Susheel Nuguru</dc:creator><description>&lt;p&gt;I think when you do not open the RTT viewer, the buffer of the logs are overflowing causing a stack corruption. Please check in your sdk_config.h file to&amp;nbsp;configure the logs buffer properly.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Make sure that you set this&amp;nbsp;NRF_LOG_ALLOW_OVERFLOW to 1. So that the oldest log buffer can be overwritten. Even though it is set to 0, it should not spill out of the logs buffer, but i am suspecting that there might be a bug there (guessing)&lt;/p&gt;
&lt;p&gt;Increase&amp;nbsp;NRF_LOG_BUFSIZE.&lt;/p&gt;
&lt;p&gt;Also do not have too many logs to print, split your logs into different categories (// &amp;lt;1=&amp;gt; Error ,// &amp;lt;2=&amp;gt; Warning,&lt;br /&gt;// &amp;lt;3=&amp;gt; Info,// &amp;lt;4=&amp;gt; Debug ) And only set&amp;nbsp;NRF_LOG_DEFAULT_LEVEL that you want to print.&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>