<?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>Where is P0.17 LED set on connect?</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/14924/where-is-p0-17-led-set-on-connect</link><description>I do not use board.h nor bsp* in my project, and also I am not initializing the pins that I do not use in my program currently - so P0.17 is not initialized and setup. However using the DK, upon connection, the LED1 P0.17 lights up. I am trying to figure</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 05 Jul 2016 15:36:06 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/14924/where-is-p0-17-led-set-on-connect" /><item><title>RE: Where is P0.17 LED set on connect?</title><link>https://devzone.nordicsemi.com/thread/56958?ContentTypeID=1</link><pubDate>Tue, 05 Jul 2016 15:36:06 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f252ebfc-bfaa-4a9c-bdf7-e3fc41a6229e</guid><dc:creator>FI</dc:creator><description>&lt;p&gt;That is confident! You are right, found the code causing the issue.  Thanks RK!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Where is P0.17 LED set on connect?</title><link>https://devzone.nordicsemi.com/thread/56957?ContentTypeID=1</link><pubDate>Mon, 04 Jul 2016 02:13:30 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:dd91596d-0d60-4521-b7b6-57914a24b432</guid><dc:creator>RK</dc:creator><description>&lt;p&gt;No the softdevice cannot be doing this. The softdevice knows nothing at all about hardware, doesn&amp;#39;t touch the GPIOs or GPIOTE, so it&amp;#39;s in your user code somewhere or in a piece of SDK code you&amp;#39;ve linked in. If you think about it, since the softdevice is designed to be used in any and all custom designs which could map pins anywhere to do anything, it can&amp;#39;t have any knowledge of GPIO nor use it them any way.&lt;/p&gt;
&lt;p&gt;Since the softdevice doesn&amp;#39;t touch output pins, or input pins, the advice is the same whether you use a softdevice or not, just leave unconnected pins at their default state on reset which is input / unconnected.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>