<?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>How can I debug a system which is using softdevice S130 in BLE uart application?</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/21041/how-can-i-debug-a-system-which-is-using-softdevice-s130-in-ble-uart-application</link><description>I want to be able to read my i2c and program logic flow within the BLE application but when I try to set breakpoints it causes the cpu to do a hard reset. How can I capture the assert condition? I also need to be able to verify that my code executes properly</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Sun, 02 Apr 2017 09:15:57 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/21041/how-can-i-debug-a-system-which-is-using-softdevice-s130-in-ble-uart-application" /><item><title>RE: How can I debug a system which is using softdevice S130 in BLE uart application?</title><link>https://devzone.nordicsemi.com/thread/82197?ContentTypeID=1</link><pubDate>Sun, 02 Apr 2017 09:15:57 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:9a3a459a-0332-4513-a7a7-10eb5ac87439</guid><dc:creator>endnode</dc:creator><description>&lt;p&gt;Nice! Just one question: have you read &lt;a href="https://devzone.nordicsemi.com/tour/"&gt;Tour guide&lt;/a&gt; (like one question per question and that you&amp;#39;ve searched the forum before asking)?:)&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How can I debug a system which is using softdevice S130 in BLE uart application?</title><link>https://devzone.nordicsemi.com/thread/82196?ContentTypeID=1</link><pubDate>Sun, 02 Apr 2017 01:50:16 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:fd4ae369-0180-4129-a433-41952a528c93</guid><dc:creator>Craig</dc:creator><description>&lt;p&gt;app_timer_start seems to be my issue I try to create a timer like so&lt;/p&gt;
&lt;p&gt;APP_TIMER_DEF(m_battery_timer_id);
err_code = app_timer_start(m_battery_timer_id, BATTERY_LEVEL_MEAS_INTERVAL, NULL);&lt;/p&gt;
&lt;p&gt;define BATTERY_LEVEL_MEAS_INTERVAL     APP_TIMER_TICKS(1000, APP_TIMER_PRESCALER)&lt;/p&gt;
&lt;p&gt;howevere I realize it looks like another timer already used in HRS but I am using this copy and paste into BLE UART example code application&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How can I debug a system which is using softdevice S130 in BLE uart application?</title><link>https://devzone.nordicsemi.com/thread/82195?ContentTypeID=1</link><pubDate>Sun, 02 Apr 2017 00:23:39 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d16bfb81-7518-4bb7-b882-514bcd1c6a77</guid><dc:creator>endnode</dc:creator><description>&lt;p&gt;You can enable UART logging (printout) and after some fiddling with baudrate and load of information you need for effective debugging you might arrive to system which tells you enough to be able to find the bugs or even optimize the code without classical break-point and step in/over debugger. In the worst case you can only use one or few GPIO pins and signal certain states by LOW/HIGH (and watch it by logical analyzer or oscilloscope). Welcome to embedded programing with time-sensitive radio stack;)&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>