<?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>TRACEDATA pins during debug</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/62985/tracedata-pins-during-debug</link><description>I know I can set the TRACEMUX pins to 0 to enable the GPIO instead of SDO. I do this on the first line of the program. 
 My problem is that when I click debug, from the time that hit debug to run, pin P1.00 is being driven high. This is unfortunately</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 29 Jun 2020 12:37:52 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/62985/tracedata-pins-during-debug" /><item><title>RE: TRACEDATA pins during debug</title><link>https://devzone.nordicsemi.com/thread/257376?ContentTypeID=1</link><pubDate>Mon, 29 Jun 2020 12:37:52 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:a929bd98-dab4-4bf1-a59e-18e855cd382f</guid><dc:creator>brett_anderson</dc:creator><description>&lt;p&gt;I found it. It was never in my code. The Segger J-link debugger has a setting that you can turn it off. For anyone else:&lt;/p&gt;
&lt;p&gt;&lt;img src="https://devzone.nordicsemi.com/resized-image/__size/320x240/__key/communityserver-discussions-components-files/4/pastedimage1593434252433v1.png" alt=" " /&gt;&lt;/p&gt;
&lt;p&gt;uncheck this box, and it will program without the SWO enabled.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: TRACEDATA pins during debug</title><link>https://devzone.nordicsemi.com/thread/257375?ContentTypeID=1</link><pubDate>Mon, 29 Jun 2020 12:34:58 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e3adda53-f756-4344-9185-0055dd57629f</guid><dc:creator>brett_anderson</dc:creator><description>&lt;p&gt;Eclipse, gcc makefile project, sdk 16.0, nRf52833.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&amp;#39;ENABLE_TRACE&amp;#39; does not exist in the project. Where would this macro be located? Is the debug module configured through the debugger, or is it compiled somewhere? If so, where is this set?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: TRACEDATA pins during debug</title><link>https://devzone.nordicsemi.com/thread/257355?ContentTypeID=1</link><pubDate>Mon, 29 Jun 2020 11:47:35 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:beb5dea0-1869-4ef0-92e8-f9e60905cbfb</guid><dc:creator>Marjeris Romero</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;We are missing some information here. For example which IDE are you using? And are you working on nRF SDK, NCS or bare metal?&lt;/p&gt;
&lt;p&gt;If you enable the ENABLE_TRACE macro when compiling, then the startup code will enable trance and configure the pins accordingly.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Some IDEs will set the device for tracing only if specified, but by default the pins are set as application GPIO pins after a reset.&lt;/p&gt;
&lt;p&gt;BR,&lt;/p&gt;
&lt;p&gt;Marjeris&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>