<?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>Connecting J-Trace with the nRF52DK</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/48102/connecting-j-trace-with-the-nrf52dk</link><description>Hi there, 
 I&amp;#39;m sorry if I&amp;#39;m asking something very simple: 
 
 How does one connect the J-Trace Pro to the nrf52 DevKit in such a way that I can get ETM functionalities? Obviously with the SWO connector via Debug-in, you can&amp;#39;t get ETM. Is there any pin</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 06 Jun 2019 11:32:11 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/48102/connecting-j-trace-with-the-nrf52dk" /><item><title>RE: Connecting J-Trace with the nRF52DK</title><link>https://devzone.nordicsemi.com/thread/191323?ContentTypeID=1</link><pubDate>Thu, 06 Jun 2019 11:32:11 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ff37e65b-6f8c-46c1-874a-a9bfde98aa5f</guid><dc:creator>brolive</dc:creator><description>&lt;p&gt;Thank&amp;#39;s the link to the other subject helped a lot, since there are the Schematics &amp;amp; Altium files of this particular adapter.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Connecting J-Trace with the nRF52DK</title><link>https://devzone.nordicsemi.com/thread/191166?ContentTypeID=1</link><pubDate>Wed, 05 Jun 2019 14:39:15 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:2b15c747-874f-4f16-a980-19cbee00bcc8</guid><dc:creator>Vidar Berg</dc:creator><description>&lt;p&gt;I think you&amp;nbsp;will need a custom adapter or find an adapter which you can solder on jumper wires to connect to the trace pins. Here&amp;#39;s a similar thread on this subject:&amp;nbsp;&lt;a href="https://devzone.nordicsemi.com/f/nordic-q-a/39398/looking-for-the-hardware-adapter-for-jtrace-connection-to-the-pca10040-development-board"&gt;link&lt;/a&gt;.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;52832&amp;nbsp;&lt;a href="https://infocenter.nordicsemi.com/topic/com.nordic.infocenter.nrf52832.ps.v1.1/pin.html#pin_assign"&gt;Pin assignments&lt;/a&gt;&amp;nbsp;for&amp;nbsp;trace&amp;nbsp;&lt;/p&gt;
&lt;table border="1" cellpadding="4" cellspacing="0" frame="border" rules="all" summary=""&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td colspan="1" headers="d14769938e72" rowspan="1" valign="top"&gt;17&lt;/td&gt;
&lt;td colspan="1" headers="d14769938e76" rowspan="1" valign="top"&gt;
&lt;p&gt;P0.14&lt;/p&gt;
&lt;p&gt;TRACEDATA[3]&lt;/p&gt;
&lt;/td&gt;
&lt;td colspan="1" headers="d14769938e80" rowspan="1" valign="top"&gt;
&lt;p&gt;Digital I/O&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;td colspan="1" headers="d14769938e84" rowspan="1" valign="top"&gt;
&lt;p&gt;General purpose I/O&lt;/p&gt;
&lt;p&gt;Trace port output&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td colspan="1" headers="d14769938e72" rowspan="1" valign="top"&gt;18&lt;/td&gt;
&lt;td colspan="1" headers="d14769938e76" rowspan="1" valign="top"&gt;
&lt;p&gt;P0.15&lt;/p&gt;
&lt;p&gt;TRACEDATA[2]&lt;/p&gt;
&lt;/td&gt;
&lt;td colspan="1" headers="d14769938e80" rowspan="1" valign="top"&gt;
&lt;p&gt;Digital I/O&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;td colspan="1" headers="d14769938e84" rowspan="1" valign="top"&gt;
&lt;p&gt;General purpose I/O&lt;/p&gt;
&lt;p&gt;Trace port output&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td colspan="1" headers="d14769938e72" rowspan="1" valign="top"&gt;19&lt;/td&gt;
&lt;td colspan="1" headers="d14769938e76" rowspan="1" valign="top"&gt;
&lt;p&gt;P0.16&lt;/p&gt;
&lt;p&gt;TRACEDATA[1]&lt;/p&gt;
&lt;/td&gt;
&lt;td colspan="1" headers="d14769938e80" rowspan="1" valign="top"&gt;
&lt;p&gt;Digital I/O&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;td colspan="1" headers="d14769938e84" rowspan="1" valign="top"&gt;
&lt;p&gt;General purpose I/O&lt;/p&gt;
&lt;p&gt;Trace port output&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td colspan="1" headers="d14769938e72" rowspan="1" valign="top"&gt;20&lt;/td&gt;
&lt;td colspan="1" headers="d14769938e76" rowspan="1" valign="top"&gt;P0.17&lt;/td&gt;
&lt;td colspan="1" headers="d14769938e80" rowspan="1" valign="top"&gt;Digital I/O&lt;/td&gt;
&lt;td colspan="1" headers="d14769938e84" rowspan="1" valign="top"&gt;General purpose I/O&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td colspan="1" headers="d14769938e72" rowspan="1" valign="top"&gt;21&lt;/td&gt;
&lt;td colspan="1" headers="d14769938e76" rowspan="1" valign="top"&gt;
&lt;p&gt;P0.18&lt;/p&gt;
&lt;p&gt;TRACEDATA[0] / SWO&lt;/p&gt;
&lt;/td&gt;
&lt;td colspan="1" headers="d14769938e80" rowspan="1" valign="top"&gt;
&lt;p&gt;Digital I/O&lt;/p&gt;
&lt;/td&gt;
&lt;td colspan="1" headers="d14769938e84" rowspan="1" valign="top"&gt;
&lt;p&gt;General purpose I/O&lt;/p&gt;
&lt;p&gt;Single wire output&lt;/p&gt;
&lt;p&gt;Trace port output&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td colspan="1" headers="d14769938e72" rowspan="1" valign="top"&gt;22&lt;/td&gt;
&lt;td colspan="1" headers="d14769938e76" rowspan="1" valign="top"&gt;P0.19&lt;/td&gt;
&lt;td colspan="1" headers="d14769938e80" rowspan="1" valign="top"&gt;Digital I/O&lt;/td&gt;
&lt;td colspan="1" headers="d14769938e84" rowspan="1" valign="top"&gt;General purpose I/O&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td colspan="1" headers="d14769938e72" rowspan="1" valign="top"&gt;23&lt;/td&gt;
&lt;td colspan="1" headers="d14769938e76" rowspan="1" valign="top"&gt;
&lt;p&gt;P0.20&lt;/p&gt;
&lt;p&gt;TRACECLK&lt;/p&gt;
&lt;/td&gt;
&lt;td colspan="1" headers="d14769938e80" rowspan="1" valign="top"&gt;
&lt;p&gt;Digital I/O&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;td colspan="1" headers="d14769938e84" rowspan="1" valign="top"&gt;
&lt;p&gt;General purpose I/O&lt;/p&gt;
&lt;p&gt;Trace port clock output&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;p&gt;&lt;br /&gt;So P0.14 should be connected to TRACEDATA[3], P0.15 to TRACEDATA[2], and so forth.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Connecting J-Trace with the nRF52DK</title><link>https://devzone.nordicsemi.com/thread/190769?ContentTypeID=1</link><pubDate>Tue, 04 Jun 2019 12:06:07 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b14e4bc5-b999-4a4d-8015-c5e200de66f8</guid><dc:creator>brolive</dc:creator><description>&lt;p&gt;I&amp;#39;m afraid it doesn&amp;#39;t really, I&amp;#39;ve red them already. In the picture of the first post mentioned, there is an adapter which isn&amp;#39;t described where to be bought or what pins it maps where to. Could you please elaborate on how the connection is supposed to be made from a 2x 10 JTAG to these pin headers on the DevKit?&lt;/p&gt;
&lt;p&gt;I know the pin mapping of the JTAG as described here on page 335 of the &lt;strong&gt;J-Link_J-Trace PDF&lt;/strong&gt;. (or image below)&lt;/p&gt;
&lt;p&gt;&lt;a href="https://www.segger.com/products/debug-probes/j-link/accessories/adapters/19-pin-cortex-m-adapter/#lightbox[435"&gt;www.segger.com/.../&lt;/a&gt;-2:320:50]&lt;/p&gt;
&lt;p&gt;And I know the pin mapping of the nRF52DK as shown in the map below.&lt;img alt=" " src="https://devzone.nordicsemi.com/resized-image/__size/720x540/__key/communityserver-discussions-components-files/4/nrf52DevKit_5F00_pinout.png" /&gt;&lt;/p&gt;
&lt;p&gt;But how do these two match?&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;E.g. where do pin numbers:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;8&lt;/li&gt;
&lt;li&gt;1&lt;/li&gt;
&lt;li&gt;11 &amp;amp; 13&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;of the JTAG Cortex-M Adapter Map to on the DevKit?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Connecting J-Trace with the nRF52DK</title><link>https://devzone.nordicsemi.com/thread/190760?ContentTypeID=1</link><pubDate>Tue, 04 Jun 2019 11:50:49 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:eddf7e1a-60d2-406f-8b08-c0765f308b55</guid><dc:creator>Vidar Berg</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;I think you will find these blog posts useful:&lt;/p&gt;
&lt;p&gt;- &lt;a href="https://devzone.nordicsemi.com/nordic/b/blog/posts/debugging-nrf52-series-devices-using-trace"&gt;https://devzone.nordicsemi.com/nordic/b/blog/posts/debugging-nrf52-series-devices-using-trace&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;- &lt;a href="https://devzone.nordicsemi.com/nordic/b/blog/posts/nrf52-tutorial-etm-instruction-trace-with-keil-mdk"&gt;https://devzone.nordicsemi.com/nordic/b/blog/posts/nrf52-tutorial-etm-instruction-trace-with-keil-mdk&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;And the pin mapping is documented in the PS here: &lt;a href="https://infocenter.nordicsemi.com/topic/com.nordic.infocenter.nrf52832.ps.v1.1/dif.html?cp=3_1_0_15_4#trace"&gt;https://infocenter.nordicsemi.com/topic/com.nordic.infocenter.nrf52832.ps.v1.1/dif.html?cp=3_1_0_15_4#trace&lt;/a&gt; &lt;span&gt;&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>