<?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>nRF52832 Real-time debug</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/41188/nrf52832-real-time-debug</link><description>I did a search on Real-time debug, it&amp;#39;s said for nRF52810, in Code generation, should set Debugging Level to Level 3, and Optimization Level to None Is that true for nRF52832, by default it set Debugging Level to Level 3, and Optimization Level to Debug</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 05 Dec 2018 01:53:48 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/41188/nrf52832-real-time-debug" /><item><title>RE: nRF52832 Real-time debug</title><link>https://devzone.nordicsemi.com/thread/160286?ContentTypeID=1</link><pubDate>Wed, 05 Dec 2018 01:53:48 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b20c6ca0-a2f4-4f77-8198-bbe33c6b3440</guid><dc:creator>zzzh</dc:creator><description>&lt;p&gt;Great.&lt;/p&gt;
&lt;p&gt;Thank you so much for the help, Jorgen.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Regards.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF52832 Real-time debug</title><link>https://devzone.nordicsemi.com/thread/160233?ContentTypeID=1</link><pubDate>Tue, 04 Dec 2018 14:39:05 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:c8370a82-f3bc-4a9f-9653-35569cd846af</guid><dc:creator>J&amp;#248;rgen Holmefjord</dc:creator><description>&lt;p&gt;I think this is referring to &lt;a href="https://www.segger.com/products/debug-probes/j-link/technology/monitor-mode-debugging/"&gt;J-Link Monitor Mode debugging&lt;/a&gt; (or similar solutions). Please have a look at &lt;a href="https://github.com/NordicPlayground/j-link-monitoring-mode-debugging/"&gt;this tutorial on Github&lt;/a&gt; for details on how to use this on the nRF52 series ICs.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF52832 Real-time debug</title><link>https://devzone.nordicsemi.com/thread/160229?ContentTypeID=1</link><pubDate>Tue, 04 Dec 2018 14:29:38 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:6c9e7781-d1a8-49dc-a1e3-127a8751c41b</guid><dc:creator>zzzh</dc:creator><description>&lt;p&gt;Hi, Jorgen,&lt;/p&gt;
&lt;p&gt;Real-time debugging will allow interrupts to execute to completion in real time when breakpoints are set&lt;br /&gt;in Thread mode or lower priority interrupts. This enables the developer to set a breakpoint and single-&lt;br /&gt;step through their code without a failure of the real-time event-driven threads running at higher priority. For&lt;br /&gt;example, this enables the device to continue to service the high-priority interrupts of an external controller or&lt;br /&gt;sensor without failure or loss of state synchronization while the developer steps through code in a low-priority&lt;br /&gt;thread.&lt;/p&gt;
&lt;p&gt;-- copied from nRF52832 Product Specification v1.4&lt;/p&gt;
&lt;p&gt;But how to set&amp;nbsp;&lt;span&gt;breakpoints&amp;nbsp;&lt;/span&gt;&lt;span&gt;in Thread mode or lower priority interrupts?&amp;nbsp; it don&amp;#39;t say.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Regards.&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF52832 Real-time debug</title><link>https://devzone.nordicsemi.com/thread/160141?ContentTypeID=1</link><pubDate>Tue, 04 Dec 2018 09:17:24 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:22fcc135-d568-4612-a16e-94d2d14ffffc</guid><dc:creator>J&amp;#248;rgen Holmefjord</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;What exactly do you mean by &amp;quot;Real-time debug&amp;quot;? Setting the Optimization level to None or -O0 is recommended when debugging, as this is the mode supported by all compilers/IDEs. You might also use Debug (-Og), if using GCC/SES. See -Og on &lt;a href="https://gcc.gnu.org/onlinedocs/gcc/Optimize-Options.html"&gt;this page&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Best regards,&lt;br /&gt;Jørgen&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>