<?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>Toggling P0.12 also toggles P0.11 on nRF52832 dev kit</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/95254/toggling-p0-12-also-toggles-p0-11-on-nrf52832-dev-kit</link><description>When I toggle pin 12, it toggles pin 11 as well. When I toggle pin 11, nothing happens. I also checked pins 13-18 to see if they were affected by both pin 11 &amp;amp; 12 and they weren&amp;#39;t. I have no code but the following running. Is there some configuration</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 02 Jan 2023 08:21:32 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/95254/toggling-p0-12-also-toggles-p0-11-on-nrf52832-dev-kit" /><item><title>RE: Toggling P0.12 also toggles P0.11 on nRF52832 dev kit</title><link>https://devzone.nordicsemi.com/thread/402744?ContentTypeID=1</link><pubDate>Mon, 02 Jan 2023 08:21:32 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:77aaf181-b252-43a2-95e9-e0c929eea12e</guid><dc:creator>Vidar Berg</dc:creator><description>&lt;p&gt;As far as I can recall, this is the first time I am hearing of&amp;nbsp;a&amp;nbsp;&lt;span&gt;short circuit&lt;/span&gt; problem on a development kit, so I am afraid I do not have a good suggestion as to what&amp;nbsp;may&amp;nbsp;have caused it. It could be something like a bad solder joint or damaged PCB trace.&lt;/p&gt;
&lt;p&gt;I suggest you ask for a replacement board if you bought it through one of our distributors.&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Toggling P0.12 also toggles P0.11 on nRF52832 dev kit</title><link>https://devzone.nordicsemi.com/thread/402703?ContentTypeID=1</link><pubDate>Fri, 30 Dec 2022 19:57:21 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:04ce0ac6-49aa-414e-9a6d-46f5aadb8d0a</guid><dc:creator>AuFries</dc:creator><description>&lt;p&gt;I just checked with a multimeter and it is a short. How can that occur?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Toggling P0.12 also toggles P0.11 on nRF52832 dev kit</title><link>https://devzone.nordicsemi.com/thread/402657?ContentTypeID=1</link><pubDate>Fri, 30 Dec 2022 11:33:43 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:88ae8bf2-3a70-4669-9822-c5eec43c5818</guid><dc:creator>Vidar Berg</dc:creator><description>&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;It&amp;nbsp;sounds like there may be a short between the pins,&amp;nbsp;or have you already measured for continuity between them?&amp;nbsp;If it is not a short,&amp;nbsp;please try to program the hex file included below and see if you still get the same result.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;a href="https://devzone.nordicsemi.com/cfs-file/__key/communityserver-discussions-components-files/4/0523.gpio_5F00_11_5F00_12_5F00_toggle_5F00_test.hex"&gt;devzone.nordicsemi.com/.../0523.gpio_5F00_11_5F00_12_5F00_toggle_5F00_test.hex&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;You can program this hex file from the command line with nrfjprog or with the Programmer app in nRF connect for desktop.&lt;/p&gt;
&lt;p&gt;With nrfjprog:&lt;/p&gt;
&lt;p&gt;$ nrfjprog --program gpio_11_12_toggle_test.hex --chiperase --reset&lt;/p&gt;
&lt;p&gt;Expected result with my hex file:&lt;/p&gt;
&lt;p&gt;&lt;img style="max-height:240px;max-width:320px;" src="https://devzone.nordicsemi.com/resized-image/__size/640x480/__key/communityserver-discussions-components-files/4/6470.pastedimage1672399814581v1.png" alt=" " /&gt;&lt;/p&gt;
&lt;p&gt;My test code (Note: fetching of the gpio binding is slightly different here as I used SDK v2.2.0)&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;pre class="ui-code" data-mode="c_cpp"&gt;/*
 * Copyright (c) 2012-2014 Wind River Systems, Inc.
 *
 * SPDX-License-Identifier: Apache-2.0
 */

#include &amp;lt;zephyr/device.h&amp;gt;
#include &amp;lt;zephyr/drivers/gpio.h&amp;gt;
#include &amp;lt;zephyr/kernel.h&amp;gt;

const struct device *mux_dev = DEVICE_DT_GET(DT_NODELABEL(gpio0));

void main(void)
{
	int err;

	printk(&amp;quot;Hello World! %s\n&amp;quot;, CONFIG_BOARD);

	err = gpio_pin_configure(mux_dev, 11, GPIO_OUTPUT | GPIO_ACTIVE_HIGH | GPIO_OUTPUT_INIT_HIGH);
	if (err) {
		printk(&amp;quot;gpio_pin_configure() failed. (%d)\n&amp;quot;, err);
	}

	err = gpio_pin_configure(mux_dev, 12, GPIO_OUTPUT | GPIO_ACTIVE_HIGH | GPIO_OUTPUT_INIT_LOW);
	if (err) {
		printk(&amp;quot;gpio_pin_configure() failed. (%d)\n&amp;quot;, err);
	}

	for (;;) {
		err = gpio_pin_toggle(mux_dev,11);
		if (err) {
			printk(&amp;quot;gpio_pin_toggle() failed. (%d)\n&amp;quot;, err);
		}

		err = gpio_pin_toggle(mux_dev,12);
		if (err) {
			printk(&amp;quot;gpio_pin_toggle() failed. (%d)\n&amp;quot;, err);
		}

		k_sleep(K_MSEC(1000));
	}
}
&lt;/pre&gt;&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Vidar&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>