Zephyr and Device Tree GPIO on Custom Board. GPIO won't turn on

RE: Zephyr and Device Tree GPIO on Custom Board. GPIO won't turn on

Nico7 — Sun, 12 May 2024 18:19:10 GMT

Thank you, for my case, I was trying to use the GPIO as an output though

RE: Zephyr and Device Tree GPIO on Custom Board. GPIO won't turn on

Nico7 — Sun, 12 May 2024 18:18:17 GMT

Ok, I just realized that in the Dev Kit there are two unpopulated resistors to be able to enable P0.03 (an P0.02) because they are otherwise NFC pins by default.

Please feel free to close this ticket as I was able to confirm that the code I presented does change the pin value, but I just couldn't see it happen because the resistors are not connected.

RE: Zephyr and Device Tree GPIO on Custom Board. GPIO won't turn on

Nico7 — Sat, 11 May 2024 08:25:28 GMT

Ok, I was able to get it going by switching to pin 0.12 as per Can't override pin assignment in .overlay.

However, I was trying to use P0.03, which connects to nft pins (nftc). so I modified my overlay file to include

&nfct {
    status = "disabled";
};

And I switched to build for the secure setting, because I'll need to access the UICR register as per: devzone.nordicsemi.com/.../config_nfct_pins_as_gpios-y-doesn-t-work

But I guess that's where I'm stuck...

RE: Zephyr and Device Tree GPIO on Custom Board. GPIO won't turn on

tejasVyas — Sat, 11 May 2024 07:44:40 GMT

Hello there,
my board do not contain button, so here what I'm doing is my gpio pin 0.2 im making it as a button.
hope you will find this example useful.
my board is xiao ble.

/ {
buttons {
compatible = "gpio-keys";
button0: button_0 {
gpios = <&gpio0 2 (GPIO_PULL_UP | GPIO_ACTIVE_LOW)>;
label = "Push button switch 0";
zephyr,code = <2>;
};

};
aliases{
sw0=&button0;
};

};