Why can't my application control the p1.00 and p1.01 pins of 5340?

RE: Why can't my application control the p1.00 and p1.01 pins of 5340?

duxinglang — Tue, 24 Feb 2026 07:23:26 GMT

Hi,

After adding these two statements to my conf file, the problem was resolved. Thank you for your help!
CONFIG_TFM_LOG_LEVEL_SILENCE=y
CONFIG_TFM_SECURE_UART=n

RE: Why can't my application control the p1.00 and p1.01 pins of 5340?

duxinglang — Tue, 24 Feb 2026 03:19:13 GMT

Hi,

Thank you for your reply. I have modified the code you provided earlier according to your instructions. The application can run on my development board, and I can see that LED1 is flashing, but LED2 does not respond at all, as shown in the attached video file.devzone.nordicsemi.com/.../e43f32ed4f36313c68ed2d192b73ce96.mp4

RE: Why can't my application control the p1.00 and p1.01 pins of 5340?

Edvin — Fri, 13 Feb 2026 14:56:05 GMT

Hello,

Try taking the app that I sent in the previous reply, and add this to prj.conf:

CONFIG_TFM_LOG_LEVEL_SILENCE=y
CONFIG_TFM_SECURE_UART=n

Then copy boards\nrf5340dk_nrf5340_cpuapp.overlay, and paste it as boards\nrf5340dk_nrf5340_cpuapp_ns.overlay

And build for nRF5340dk/nrf5340/cpuapp/ns, and see if that works.

Best regards,

Edvin

RE: Why can't my application control the p1.00 and p1.01 pins of 5340?

duxinglang — Thu, 29 Jan 2026 01:45:28 GMT

Sorry, I made a mistake earlier and wrote it as ncs2.3.0, but it's actually ncs2.7.0. I added `/delete-node/ &gpio_fwd;` in my overlay file, but it didn't work, even though it's no longer found in the compiled zephyr.dts file. I confirm that my project has no other sub-images, which can be verified from the build folder.

devzone.nordicsemi.com/.../8524.zephyr.dts

RE: Why can't my application control the p1.00 and p1.01 pins of 5340?

Edvin — Wed, 28 Jan 2026 14:07:17 GMT

I am struggling to understand your application, but I was able to build it using v2.7.0 (see that you edited it, but it said v2.3.0 before).

The pins are set as inputs, even if I completely remove the lines that you highlighted, so they are set from somewhere else.

I modified the peripheral_uart sample to toggle these GPIOs:

devzone.nordicsemi.com/.../peripheral_5F00_uart_5F00_53.zip

They are toggled from main.c:

	for (;;) {
		dk_set_led(RUN_STATUS_LED0, (++blink_status) % 2);
		dk_set_led(RUN_STATUS_LED1, (blink_status) % 2);
		dk_set_led(RUN_STATUS_LED2, (blink_status) % 2);
		k_sleep(K_MSEC(RUN_LED_BLINK_INTERVAL));
	}

And I changed the Led 1 and 2 to P1.00 and P1.01 in boards\nrf5340dk_nrf5340_cpuapp.overlay.

I also added the line:

/delete-node/ &gpio_fwd;

in that file.

Please note that if you have any sub-images (because I don't think you are using sysbuild?) such as mcuboot or an immutable bootloader, that also runs on the app core, you need to disable the gpio_fwd in their respective board files as well.

Best regards,

Edvin

RE: Why can't my application control the p1.00 and p1.01 pins of 5340?

duxinglang — Tue, 27 Jan 2026 10:06:34 GMT

OK, I have uploaded the entire application, and you can track the status of pins p1.00 and p1.01 step by step according to my screenshot.

By the way, I am using the version ncs2.7.0.

devzone.nordicsemi.com/.../5340_5F00_NCS2.7.0_5F00_TEST.rar

RE: Why can't my application control the p1.00 and p1.01 pins of 5340?

Edvin — Tue, 27 Jan 2026 09:48:48 GMT

Can you please upload the full application (or at least an application that can reproduce the issue), so that I can try to reproduce it locally?

Best regards,

Edvin

RE: Why can't my application control the p1.00 and p1.01 pins of 5340?

duxinglang — Tue, 27 Jan 2026 08:53:32 GMT

Yes, i test it on the DK board, However, I have already set up to output log information from the SWD interface via Rtt. Moreover, on our client's board, these two pins are also uncontrollable.

RE: Why can't my application control the p1.00 and p1.01 pins of 5340?

Edvin — Tue, 27 Jan 2026 08:41:07 GMT

Are you testing this on an nRF5340 DK? If so, the pins are connected to the debugger. Flash the application, power cycle the DK, and make sure not to start a debug session (By opening an UART or RTT terminal, which will activate the debugger, which will control the UART pins).

BR,

Edvin

RE: Why can't my application control the p1.00 and p1.01 pins of 5340?

duxinglang — Tue, 27 Jan 2026 07:43:04 GMT

No，I can confirm that gpio_audio points to gpio1, WTN_DATA is defined as pin 1, and WTN_BUSY is defined as 0, which means these two pins are p1.00 and p1.01 respectively.

RE: Why can't my application control the p1.00 and p1.01 pins of 5340?

Turbo J — Tue, 27 Jan 2026 07:14:43 GMT

PIN_CNF says: DIR Input. No pullup or pulldown enabled. That also means the output drivers are disabled.

The code looks funny, check what device gpio_audio actually points to. Might be the wrong GPIO or a totally wrong device altogether.

RE: Why can't my application control the p1.00 and p1.01 pins of 5340?

duxinglang — Tue, 27 Jan 2026 01:29:59 GMT

Thanks for your help. I added the statement you mentioned, but it didn't work. p1.00 and p1.01 still cannot be pulled up or down. Here is the relevant screenshot.

RE: Why can't my application control the p1.00 and p1.01 pins of 5340?

Edvin — Mon, 26 Jan 2026 11:28:02 GMT

Hello,

Try adding this to your nrf5340dk_nrf5340_cpuapp_ns.overlay:

/delete-node/ &gpio_fwd;

I don't have your application to test, but after you do, if it doesn't work as intended, can you please try to run a debug session, and view the GPIO1 registers, particularly the PIN_CNF[0] and [1]. The first bit should be 0 (unlike it is in this screenshot) if the pins are controlled by the application core:

The MCUSEL field should say "AppMCU" if the pin_fwd is successfully disabled.

Best regards,

Edvin