<?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>nrf52840 QFN48 pin debugging</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/126933/nrf52840-qfn48-pin-debugging</link><description>Hello, 
 I&amp;#39;ve got a nrf52840 DK to flash custom PCB with nrf52840 QFN. I can flash the custom PCB by using &amp;lt;nrfjprog&amp;gt; command into VSCode but the code doesn&amp;#39;t seem to work. The short code is intended to verify if the chip is alive by setting physical</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 23 Feb 2026 17:25:31 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/126933/nrf52840-qfn48-pin-debugging" /><item><title>RE: nrf52840 QFN48 pin debugging</title><link>https://devzone.nordicsemi.com/thread/561882?ContentTypeID=1</link><pubDate>Mon, 23 Feb 2026 17:25:31 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:7e18766d-c340-4982-8033-4c8c55cb9c8d</guid><dc:creator>luke1295</dc:creator><description>&lt;p&gt;Yes, the schematic and layout are good. I will try to design again QFN type with low oscillator and inductors for DCDC.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrf52840 QFN48 pin debugging</title><link>https://devzone.nordicsemi.com/thread/561767?ContentTypeID=1</link><pubDate>Sun, 22 Feb 2026 12:47:39 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:4dd61aa3-e463-4ade-9c44-1aa9b1e21045</guid><dc:creator>Kenneth</dc:creator><description>&lt;p&gt;Have someone reviewed your schematic and layout? Maybe make a private case so someone can take a look.&lt;/p&gt;
&lt;p&gt;I can&amp;#39;t find anything specific wrong here, so maybe the hardware is outside of specifications.&lt;/p&gt;
&lt;p&gt;Kenneth&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrf52840 QFN48 pin debugging</title><link>https://devzone.nordicsemi.com/thread/561758?ContentTypeID=1</link><pubDate>Sat, 21 Feb 2026 09:43:28 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:a738dfc3-03c4-4d11-851f-d3fb0cb0acb2</guid><dc:creator>luke1295</dc:creator><description>&lt;p&gt;&lt;a href="https://devzone.nordicsemi.com/cfs-file/__key/communityserver-discussions-components-files/4/text_5F00_config2.txt"&gt;devzone.nordicsemi.com/.../text_5F00_config2.txt&lt;/a&gt;&lt;a href="https://devzone.nordicsemi.com/cfs-file/__key/communityserver-discussions-components-files/4/text_5F00_config.txt"&gt;devzone.nordicsemi.com/.../text_5F00_config.txt&lt;/a&gt;&lt;a href="https://devzone.nordicsemi.com/cfs-file/__key/communityserver-discussions-components-files/4/8688.zephyr.dts"&gt;devzone.nordicsemi.com/.../8688.zephyr.dts&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Sure, here are the files. I kept prj.conf as in the beginning. Also, I&amp;#39;ve tried in .overlay:&lt;br /&gt;&lt;pre class="ui-code" data-mode="text"&gt;&amp;amp;reg1 {
	regulator-initial-mode = &amp;lt;0x0&amp;gt;;
};

&amp;amp;reg0 {
    status = &amp;quot;okay&amp;quot;;
};&lt;/pre&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrf52840 QFN48 pin debugging</title><link>https://devzone.nordicsemi.com/thread/561588?ContentTypeID=1</link><pubDate>Thu, 19 Feb 2026 12:13:52 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:91923be9-9b7b-47d3-b4b1-04e101edf575</guid><dc:creator>Kenneth</dc:creator><description>&lt;p&gt;Can you share the updated zephyr.dts file(s) and .config file(s) after this change to make sure all are indeed set to 0x0 and also make sure all are using the internal RC oscillator.&lt;/p&gt;
&lt;p&gt;Kenneth&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrf52840 QFN48 pin debugging</title><link>https://devzone.nordicsemi.com/thread/561292?ContentTypeID=1</link><pubDate>Mon, 16 Feb 2026 18:51:47 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:897d0861-9cd0-4586-9a04-3598a5da178f</guid><dc:creator>luke1295</dc:creator><description>&lt;p&gt;Hi,&lt;br /&gt; I&amp;#39;ve tried to modify in zephyr.dts regulator-initial-mode = &amp;lt; 0x0 &amp;gt;; and also in overlay file as:&lt;/p&gt;
&lt;p&gt;&lt;pre class="ui-code" data-mode="text"&gt;&amp;amp;reg1 {
	regulator-initial-mode = &amp;lt;0x0&amp;gt;;
};&lt;/pre&gt;&lt;/p&gt;
&lt;p&gt;Also, dead in standalone power supply but alive in debug mode. Other possible causes to not starting?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrf52840 QFN48 pin debugging</title><link>https://devzone.nordicsemi.com/thread/561223?ContentTypeID=1</link><pubDate>Mon, 16 Feb 2026 11:59:06 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:5ec46272-3e37-4e44-bf61-dd1b7ed54e24</guid><dc:creator>Kenneth</dc:creator><description>&lt;p&gt;Looking at the zephyr.dts I can find:&lt;/p&gt;
&lt;p&gt;&lt;pre class="ui-code" data-mode="text"&gt;			/* node &amp;#39;/soc/power@40000000/regulator@40000578&amp;#39; defined in zephyr\dts\arm\nordic\nrf52840.dtsi:96 */
			reg1: regulator@40000578 {
				compatible = &amp;quot;nordic,nrf5x-regulator&amp;quot;; /* in zephyr\dts\arm\nordic\nrf52840.dtsi:97 */
				reg = &amp;lt; 0x40000578 0x1 &amp;gt;;              /* in zephyr\dts\arm\nordic\nrf52840.dtsi:98 */
				regulator-name = &amp;quot;REG1&amp;quot;;               /* in zephyr\dts\arm\nordic\nrf52840.dtsi:99 */
				regulator-initial-mode = &amp;lt; 0x1 &amp;gt;;      /* in zephyr\boards\nordic\nrf52840dk\nrf52840dk_nrf52840.dts:150 */
			};&lt;/pre&gt;&lt;/p&gt;
&lt;p&gt;regulator-initial-mode seems to be set to&amp;nbsp;NRF5X_REG_MODE_DCDC (=1) and not&amp;nbsp;NRF5X_REG_MODE_LDO (=0).&lt;/p&gt;
&lt;p&gt;Kenneth&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrf52840 QFN48 pin debugging</title><link>https://devzone.nordicsemi.com/thread/561174?ContentTypeID=1</link><pubDate>Sat, 14 Feb 2026 21:43:10 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:9ec8f7d9-1575-4b23-b3dc-00e4a833d1fb</guid><dc:creator>luke1295</dc:creator><description>&lt;p&gt;UPDATE:&lt;br /&gt;&lt;br /&gt;I managed to toggle physical pin 14 (P0.14) and 15&amp;nbsp;&lt;span&gt;(P0.17)&amp;nbsp;from the debugger. But when I power-on the chip standalone it doesn&amp;#39;t start. I measured the correct voltages on DEC pins (stable voltages). I measured the nRESET pin and its 0V. No short on the PCB.&lt;br /&gt;&lt;br /&gt;I observed&amp;nbsp;a weird behavior. For a new chip, 1st use from reel, I can successfully connect from the debugger. After I flash the code, I cannot connect easily. I need to connect in the first second window after power-on the chip. I tried with J-Flash program (Connect option) and its the same story. Its something I broke after flashing by using nrfjprog commands? And that&amp;#39;s why my chip seems to be dead in normal operation but in debug mode I can toggle the pins? Its something that keeps the chip into reset state?&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrf52840 QFN48 pin debugging</title><link>https://devzone.nordicsemi.com/thread/560843?ContentTypeID=1</link><pubDate>Tue, 10 Feb 2026 19:49:39 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:df6f168a-2c3f-43d6-b438-8347483144ed</guid><dc:creator>luke1295</dc:creator><description>&lt;p&gt;&lt;a href="https://devzone.nordicsemi.com/cfs-file/__key/communityserver-discussions-components-files/4/Copy2_2E00_config"&gt;devzone.nordicsemi.com/.../Copy2_2E00_config&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrf52840 QFN48 pin debugging</title><link>https://devzone.nordicsemi.com/thread/560841?ContentTypeID=1</link><pubDate>Tue, 10 Feb 2026 19:48:11 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:8beb1610-c710-4082-b7c3-a4d66809401c</guid><dc:creator>luke1295</dc:creator><description>&lt;p&gt;&lt;a href="https://devzone.nordicsemi.com/cfs-file/__key/communityserver-discussions-components-files/4/Copy_2E00_config"&gt;devzone.nordicsemi.com/.../Copy_2E00_config&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Dts here:&amp;nbsp;&lt;a href="https://devzone.nordicsemi.com/cfs-file/__key/communityserver-discussions-components-files/4/4380.zephyr.dts"&gt;devzone.nordicsemi.com/.../4380.zephyr.dts&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Sure. I found 2x .config. One in: project_name/build/project_name/zephyr and one in: project_name/build/zephyr&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrf52840 QFN48 pin debugging</title><link>https://devzone.nordicsemi.com/thread/560839?ContentTypeID=1</link><pubDate>Tue, 10 Feb 2026 19:29:16 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:29ce0cb2-b6f5-457c-8be4-caa92e995cf8</guid><dc:creator>Kenneth</dc:creator><description>&lt;p&gt;Can you share the .config and zephyr.dts files from your build folder?&lt;/p&gt;
&lt;p&gt;Kenneth&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrf52840 QFN48 pin debugging</title><link>https://devzone.nordicsemi.com/thread/560838?ContentTypeID=1</link><pubDate>Tue, 10 Feb 2026 18:52:02 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b05f2e20-87dd-4c9f-8edf-199b1fb5abb5</guid><dc:creator>luke1295</dc:creator><description>&lt;p&gt;Hi,&lt;br /&gt;&lt;br /&gt;I&amp;#39;ve tried the following code for multiple GPIO:&lt;/p&gt;
&lt;p&gt;&lt;pre class="ui-code" data-mode="text"&gt;#define PIN_P0_13 13
#define PIN_P0_14 14
#define PIN_P0_15 15
#define PIN_P1_15 38

int main(void)
{
    const struct device *gpio0 = DEVICE_DT_GET(DT_NODELABEL(gpio0));
    const struct device *gpio1 = DEVICE_DT_GET(DT_NODELABEL(gpio1));

    if (!device_is_ready(gpio0) || !device_is_ready(gpio1)) {
        return 0;
    }


    gpio_pin_configure(gpio0, PIN_P0_13, GPIO_OUTPUT_INACTIVE);
    gpio_pin_configure(gpio0, PIN_P0_14, GPIO_OUTPUT_INACTIVE);
    gpio_pin_configure(gpio0, PIN_P0_15, GPIO_OUTPUT_INACTIVE);
    gpio_pin_configure(gpio1, PIN_P1_15, GPIO_OUTPUT_ACTIVE);

    while (1) {
        gpio_pin_set(gpio0, PIN_P0_13, 1);
        gpio_pin_set(gpio0, PIN_P0_14, 1);
        gpio_pin_set(gpio0, PIN_P0_15, 1);
        gpio_pin_set(gpio1, PIN_P1_15, 1);
        k_msleep(500);

        gpio_pin_set(gpio0, PIN_P0_13, 0);
        gpio_pin_set(gpio0, PIN_P0_14, 0);
        gpio_pin_set(gpio0, PIN_P0_15, 0);
        gpio_pin_set(gpio1, PIN_P1_15, 0);
        k_msleep(500);
    }
}&lt;/pre&gt;&lt;/p&gt;
&lt;p&gt;On DK the code is working since LED1, LED2 and LED3 are blinking. On QFN nothing happens. My overlay file is called: nrf54h20dk_nrf54h20_cpuppr.overlay and the content is this:&lt;br /&gt;&lt;br /&gt;&lt;pre class="ui-code" data-mode="text"&gt;&amp;amp;reg1 {
	regulator-initial-mode = &amp;lt;NRF5X_REG_MODE_LDO&amp;gt;;
};

&amp;amp;reg0 {
    status = &amp;quot;okay&amp;quot;;
};&lt;/pre&gt;&lt;/p&gt;
&lt;p&gt;I&amp;#39;ve tried to enter in debug mode both for DK and for connected QFN. I can step each line without any error. Is something I&amp;#39;m missing about GPIO when I&amp;#39;m migrating the code on QFN?&lt;br /&gt;&lt;br /&gt;Luke&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrf52840 QFN48 pin debugging</title><link>https://devzone.nordicsemi.com/thread/560757?ContentTypeID=1</link><pubDate>Tue, 10 Feb 2026 09:22:09 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:9a1a7576-a3a3-4b2f-9e6f-f22bce2d90fa</guid><dc:creator>Kenneth</dc:creator><description>&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;If you have problems with a specific GPIO, my first suggestion for test would be to try a different GPIO.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;The firmware should be able to run on both DK and your board, does it work as intended on the DK?&lt;/p&gt;
&lt;p&gt;Also look a the .config and zephyr.dts file from the build folder, is it possible that P0.13 is already use for LED or similar?&amp;nbsp;&lt;/p&gt;
&lt;p&gt;If you try to debug your project in vs code, can you single step the project to see if it faults or execute as expected?&lt;/p&gt;
&lt;p&gt;Kenneth&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>