<?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>Unable to run UART BLE app example without debugger</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/37477/unable-to-run-uart-ble-app-example-without-debugger</link><description>Greetings. Finally ordered some NRF52832 board from HOLY IOT and spend few weeks trying to handle with them. 
 So, all about setup: 
 SDK: 15 (15.0.0_a53641a) @ Windows 7 x64 
 IDE: Segger (Embedded Studio) 
 SD: 132 (s132_nrf52_3.1.0) 
 HW: custom board</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 19 Sep 2018 16:05:53 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/37477/unable-to-run-uart-ble-app-example-without-debugger" /><item><title>RE: Unable to run UART BLE app example without debugger</title><link>https://devzone.nordicsemi.com/thread/149498?ContentTypeID=1</link><pubDate>Wed, 19 Sep 2018 16:05:53 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:dc3ed5ef-a815-4828-8a1c-6f56ad6a8b07</guid><dc:creator>kalauffenburger</dc:creator><description>&lt;p&gt;Never mind, I figured out the issue that I was having.&lt;/p&gt;
&lt;p&gt;The problem was that I was calling app_usbd_power_events_enable() before initializing the BLE stack (and therefore before enabling the softdevice).&lt;/p&gt;
&lt;p&gt;--ken&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Unable to run UART BLE app example without debugger</title><link>https://devzone.nordicsemi.com/thread/149322?ContentTypeID=1</link><pubDate>Tue, 18 Sep 2018 19:26:44 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:717e43df-b0bd-4267-b46a-da074a6fb5e3</guid><dc:creator>kalauffenburger</dc:creator><description>&lt;p&gt;I forgot to mention, I have removed calls to printf() and it still does not work.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Unable to run UART BLE app example without debugger</title><link>https://devzone.nordicsemi.com/thread/149320?ContentTypeID=1</link><pubDate>Tue, 18 Sep 2018 19:03:23 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:50cfab8e-e989-4bb4-8354-eff6abc48453</guid><dc:creator>kalauffenburger</dc:creator><description>&lt;p&gt;jeremysf,&lt;/p&gt;
&lt;p&gt;Were you able to resolve this problem?&amp;nbsp; I am seeing exactly the same problem you describe.&amp;nbsp; I also have a custom hardware and so working with the example application is not easily done without significant reconfiguration.&lt;/p&gt;
&lt;p&gt;This problem did not occur using SDK nRF5_SDK_14.2.0_17b948a, but showed up when I ported the code to use SDK nRF5_SDK_15.1.0_a8c0c4d.&lt;/p&gt;
&lt;p&gt;I&amp;#39;m not sure how to debug the problem other than using shotgun techniques.&lt;/p&gt;
&lt;p&gt;--ken&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Unable to run UART BLE app example without debugger</title><link>https://devzone.nordicsemi.com/thread/145723?ContentTypeID=1</link><pubDate>Fri, 24 Aug 2018 17:43:25 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:732256a2-dcb3-44f2-ad85-75a9a05336e2</guid><dc:creator>jeremysf</dc:creator><description>&lt;p&gt;I am having the same issue with my own hardware design. USB CDC works great with the debugger is attached (i.e. JLinkExe is running). I can reset the device, and plug/un-plug the USB cable. When I quit JLinkExe,&amp;nbsp;the USB device is still present and things work. If I unplug and replug the USB cable,&amp;nbsp;(with JLinkExe not running) then&amp;nbsp;there is no discovery.&lt;/p&gt;
&lt;p&gt;I did not have retarget.c linked into my project, but I am using SEGGER RTT. I tried to disable logs via setting NRF_LOG_ENABLED to false (and I see no logs) but that had no effect on the issue.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Unable to run UART BLE app example without debugger</title><link>https://devzone.nordicsemi.com/thread/144292?ContentTypeID=1</link><pubDate>Wed, 15 Aug 2018 10:41:00 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:027d75ed-47fe-4190-902e-25c5646eeb7f</guid><dc:creator>jerry2107</dc:creator><description>&lt;p&gt;Dear H&amp;aring;kon, thanks for fast answer!&lt;/p&gt;
&lt;p&gt;Yes, i faced that problem with putchar, but instead of correct solution i just commented that part (yep, project was not touched, but retarget.c was modified and i forgot about that...).&lt;/p&gt;
&lt;p&gt;Once i tried solution from link (proper type for parameter) - its became stable, example works exactly as expected.&lt;/p&gt;
&lt;p&gt;Thanks a lot !&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Unable to run UART BLE app example without debugger</title><link>https://devzone.nordicsemi.com/thread/144279?ContentTypeID=1</link><pubDate>Wed, 15 Aug 2018 09:12:42 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:cfffec45-9b74-4658-9f5a-0f72e8d73257</guid><dc:creator>H&amp;#229;kon Alseth</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;That module looks to have a &amp;quot;full reference design&amp;quot;, meaning it has DCDC components, external 32k oscillator.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Do other examples work just fine, for instance ble_app_hrs?&lt;/p&gt;
&lt;p&gt;There is a currently known issue with newer versions of SES, and standard functions for input/output:&lt;/p&gt;
&lt;p&gt;&lt;a href="https://devzone.nordicsemi.com/f/nordic-q-a/34784/conflicting-types-for-_putchar/133776#133776"&gt;https://devzone.nordicsemi.com/f/nordic-q-a/34784/conflicting-types-for-_putchar/133776#133776&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;If you have removed retarget.c from your project, I suspect printf is redirected to a &lt;a href="https://studio.segger.com/index.htm?https://studio.segger.com/libc_customizing_putchar.htm"&gt;inbuilt debug print&lt;/a&gt; instead. This would only work if you enter debug mode. You could try to remove the calls to printf and see if it works better?&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Håkon&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>