<?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>ITM on custom nRF52 device through DK</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/31083/itm-on-custom-nrf52-device-through-dk</link><description>I&amp;#39;m developing custom PCB with the nRF52832, and I would like to use the ITM for debugging. I don&amp;#39;t have a J-trace or equivalent hardware, so everything will have to be done via the nRF52 DK. Am I correct in assuming it is enough to simply route the TRACEDATA</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 05 Mar 2018 14:17:14 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/31083/itm-on-custom-nrf52-device-through-dk" /><item><title>RE: ITM on custom nRF52 device through DK</title><link>https://devzone.nordicsemi.com/thread/122849?ContentTypeID=1</link><pubDate>Mon, 05 Mar 2018 14:17:14 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:5a7e15a5-8b17-4b7c-846a-09cfa6fd3523</guid><dc:creator>meshs</dc:creator><description>&lt;p&gt;Thank you Edvin! Could you comment on the question regarding the pull-up on the reset-line I edited into the first post? Basically I&amp;#39;m worried that the 10k pullup may interfere with debug operations.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: ITM on custom nRF52 device through DK</title><link>https://devzone.nordicsemi.com/thread/122843?ContentTypeID=1</link><pubDate>Mon, 05 Mar 2018 14:02:08 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:93ea5825-c2b9-4a3e-9511-b6a961068edc</guid><dc:creator>Edvin</dc:creator><description>&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;You will also have to set up the SWO module. Please see Rick&amp;#39;s answer in &lt;a href="https://devzone.nordicsemi.com/f/nordic-q-a/27855/using-swo-with-nrf52-redux" rel="noopener noreferrer" target="_blank"&gt;this thread&lt;/a&gt; on how to do this.&lt;/p&gt;
&lt;p&gt;Try to get this up and running on the DK before switching to the custom PCB.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Then you can use the external debugger (P19) to debug your custom PCB. Please note that there was a bug in the previous versions of the segger firmware, causing the segger chip on the DK to not switch to the external SWO pin on P19 when an external device is connected. The fix is to install JLink version 6.22f, and update the On Board (OB) Segger chip. (you will get prompted with this the next time you try to use e.g. nrfjprog the JLink firmware after updating to 6.22f). Alternatively you can solder SWO_EXT to P0.18 on the development kit that you use to debug the custom PCB.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Then the external SWO debugging on the DK should work.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Edvin&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>