<?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>For pins that are common on the nRF52832, is there anything specific you need to do to define their desired I/O?</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/23059/for-pins-that-are-common-on-the-nrf52832-is-there-anything-specific-you-need-to-do-to-define-their-desired-i-o</link><description>Hardware: redbearlabs Nano V2 (see pinout below)
Programmer: DAPLink v1.5 supplied by redbear
IDE: Arduino with the redbearlab nano 2 board package 
 
 The schematic can be found here: github.com/.../Nano V2.0 SCH 20161102.pdf 
 Specifically, I&amp;#39;ve</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 06 Jul 2017 05:21:02 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/23059/for-pins-that-are-common-on-the-nrf52832-is-there-anything-specific-you-need-to-do-to-define-their-desired-i-o" /><item><title>RE: For pins that are common on the nRF52832, is there anything specific you need to do to define their desired I/O?</title><link>https://devzone.nordicsemi.com/thread/90755?ContentTypeID=1</link><pubDate>Thu, 06 Jul 2017 05:21:02 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:089d4166-25a8-4b85-927a-444f0bd789bb</guid><dc:creator>Turbo J</dc:creator><description>&lt;p&gt;That link 404s here.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: For pins that are common on the nRF52832, is there anything specific you need to do to define their desired I/O?</title><link>https://devzone.nordicsemi.com/thread/90758?ContentTypeID=1</link><pubDate>Tue, 27 Jun 2017 08:29:03 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:5b5b1d5b-363b-4114-ac17-31240454657b</guid><dc:creator>FormerMember</dc:creator><description>&lt;p&gt;Any GPIO can be used to everything. How do you configure the GPIOs?&lt;/p&gt;
&lt;p&gt;Could you test the following: Configure the &amp;quot;problematic&amp;quot; pins as output pins, and set the firmware to toggle the pins a couple of times. Then: Run the chip in debug mode/step through the code and monitor the values of the GPIOs as they are being toggled.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: For pins that are common on the nRF52832, is there anything specific you need to do to define their desired I/O?</title><link>https://devzone.nordicsemi.com/thread/90756?ContentTypeID=1</link><pubDate>Tue, 27 Jun 2017 01:22:47 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e3465272-8886-4d56-ad35-246075c5ae5e</guid><dc:creator>Bashir</dc:creator><description>&lt;p&gt;Added link to schematic. Thanks for the suggestion.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: For pins that are common on the nRF52832, is there anything specific you need to do to define their desired I/O?</title><link>https://devzone.nordicsemi.com/thread/90757?ContentTypeID=1</link><pubDate>Mon, 26 Jun 2017 20:27:30 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e75809db-30b9-4676-9bce-9bddd0412bee</guid><dc:creator>Turbo J</dc:creator><description>&lt;p&gt;We would need a &lt;em&gt;real&lt;/em&gt; schematic - including all connections - to answer your question.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>