Blue LED really "GPIO_ACTIVE_LOW"?

AchimKraus

I use “gpio_pin_set_dt” to switch LEDs. On the nRF9160-DK and the Thingy:91 that works as expected. On the feather it seems to be inverted. The device tree contains

leds {
	compatible = "gpio-leds";
	blue_led: led_0 {
		gpios = <&gpio0 3 GPIO_ACTIVE_LOW>;
		label = "Blue LED (D7)";
	};
};

is the GPIO_ACTIVE_LOW checked?
(If I replace GPIO_ACTIVE_LOW with 0 it works as expected with NCS-2.1.2.)

jaredwolff

On the v5 the LED is GPIO_ACTIVE_HIGH so you’ll need to create an overlay to fix it.

AchimKraus

OK.

AchimKraus

If I change it in the overlay, it seems to apply that to the boot-loader as well, and with that, the led doesn’t longer indicate the bootloader mode. Is there a way to fix it also for the bootloader?

AchimKraus

I found it:
though I usually build with the ncs-tools, that requires the overlay in “child_image/mcuboot/boards”. The file name is “circuitdojo_feather_nrf9160.overlay” (without “ns”). With that the LED indicates the bootmode again.

jaredwolff

Missed this one. Glad you got it working!

For a while the GPIO configuration was in the the board .conf overlay. I think someone more recently Zephyr-fied it and used the device tree definitions instead.