<?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>nRF52840 - How to debug Zephyr code when the radio is running. HardFault</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/69392/nrf52840---how-to-debug-zephyr-code-when-the-radio-is-running-hardfault</link><description>Hi, I found that after migration from Zigbee Thread SDK to Zephyr GDB debugging functionality is broken. I have read a lot about PRIMASK register, GDB hooks, and so on, but those didn&amp;#39;t fix all of my problems. I want to use Eclipse + GDB for stepping</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 15 Dec 2020 09:13:22 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/69392/nrf52840---how-to-debug-zephyr-code-when-the-radio-is-running-hardfault" /><item><title>RE: nRF52840 - How to debug Zephyr code when the radio is running. HardFault</title><link>https://devzone.nordicsemi.com/thread/284966?ContentTypeID=1</link><pubDate>Tue, 15 Dec 2020 09:13:22 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:962cb3cf-7a23-4b57-b75e-6264552f6c4e</guid><dc:creator>naps</dc:creator><description>&lt;p&gt;I will dig into this topic and will try to provide some universal open-source solution and post it here in this thread.&lt;br /&gt;Thanks for your help.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF52840 - How to debug Zephyr code when the radio is running. HardFault</title><link>https://devzone.nordicsemi.com/thread/284866?ContentTypeID=1</link><pubDate>Mon, 14 Dec 2020 16:40:30 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:1c77fdd3-1c2c-48af-9b63-6074b9ccbc93</guid><dc:creator>J&amp;#248;rgen Holmefjord</dc:creator><description>&lt;p&gt;I have only tested MMD with nRF5 SDK, and the instructions in the GitHub tutorial I linked, not together with NCS or Zigbee, but I did only run it on a standard nRF52 DK. No modifications were made to the DK or J-Link FW.&lt;/p&gt;
&lt;p&gt;If you have the required files and commands in place, I believe you should be able to run it with the DK as well.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;You may get some better answers regarding exactly why it does not work in the &lt;a href="https://forum.segger.com/"&gt;Segger Forums&lt;/a&gt;.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF52840 - How to debug Zephyr code when the radio is running. HardFault</title><link>https://devzone.nordicsemi.com/thread/284861?ContentTypeID=1</link><pubDate>Mon, 14 Dec 2020 16:19:39 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:700b1ce9-5d70-4d84-bb28-6d9da7d92d2f</guid><dc:creator>naps</dc:creator><description>&lt;p&gt;&lt;span&gt;Hi, thanks for your fast reply.&lt;br /&gt;We are using nRF Connect SDK for the Zigbee application and building it with west + makefiles.&lt;br /&gt;According to&amp;nbsp;&lt;a href="https://www.segger.com/products/debug-probes/j-link/technology/monitor-mode-debugging/"&gt;www.segger.com/.../&lt;/a&gt;&lt;br /&gt;&lt;/span&gt;&lt;/p&gt;
&lt;h4 class="element-header " id="do-all-j-links-support-monitor-mode-debugging"&gt;&lt;span&gt;Do all J-Links support Monitor Mode Debugging?&lt;/span&gt;&lt;/h4&gt;
&lt;p&gt;&lt;strong&gt;A:&lt;/strong&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;No, Monitor Mode Debugging is only supported by J-Link PLUS, PRO, ULTRA+, and J-Trace. J-Link BASE and on-board J-Links cannot be used for Monitor Mode Debugging&lt;br /&gt;&lt;br /&gt;I&amp;#39;m wondering if it is really possible.&lt;br /&gt;&lt;br /&gt;I&amp;#39;m using opensource toolchains and IDE, and&amp;nbsp;I was able to run MMD by compiling some parts of the sample project from Segger. Next, I&amp;#39;ve added some gdb commands for init&amp;nbsp;&lt;br /&gt;&lt;br /&gt;mon reset 0&lt;br /&gt;mon exec SetMonModeDebug=1&lt;br /&gt;mon exec SetMonModeVTableAddr=0x1f000&lt;br /&gt;&lt;br /&gt;And It just works, but only using our external JTrace probe.&lt;br /&gt;You mention some additional licenses; is it possible to upgrade onboard nrf52 devkit JLlink? Or should it work out of the box in your opinion, if our second (JTrace) configuration is working?&amp;nbsp;&lt;br /&gt;&lt;br /&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF52840 - How to debug Zephyr code when the radio is running. HardFault</title><link>https://devzone.nordicsemi.com/thread/284580?ContentTypeID=1</link><pubDate>Fri, 11 Dec 2020 14:48:58 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:93cdd1dd-4399-4371-960b-d9dd98cd614e</guid><dc:creator>J&amp;#248;rgen Holmefjord</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;Are you using Zephyr directly, or nRF Connect SDK? Which protocol are you using (Zigbee/Thread/BLE)?&lt;/p&gt;
&lt;p&gt;Monitor Mode Debugging can be run on our nRF52 DKs in evaluation mode, see &lt;a href="https://github.com/NordicPlayground/j-link-monitoring-mode-debugging"&gt;this tutorial&lt;/a&gt;. For commercial use, you will have to get a license from Segger.&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>