LEDs inverted with nRF Connect SDK DK Button and LEDs

[brec]

Greetings,

CPU = nRF5340

SDK = nRF Connect SDK v1.6.1 and 1.6.0

Board = custom

For the nRF5430, we have a custom board that uses active high logic to turn LEDs on. In the custom board's DTS files, we set GPIO_ACTIVE_HIGH:

	leds {
				compatible = "gpio-leds";
				led0: led_0 {
					gpios = <&gpio1 4 GPIO_ACTIVE_HIGH>;
					label = "RED LED 0";
				};
				led1: led_1 {
					gpios = <&gpio0 25 GPIO_ACTIVE_HIGH>;
					label = "Green LED 1";
				};
				led2: led_2 {
					gpios = <&gpio1 6 GPIO_ACTIVE_HIGH>;
					label = "BLUE LED 2";
				};
			};

When using the peripheral_lbs sample code, All three LEDs operate in exactly the opposite fashion. Red just flashes, but suspect it starts in the opposite state. Green in ON when disconnected and off when connected. Blue is on to start, then turns off when writing a non-zero value to the characteristic and on when writing a zero.

We have other code that utilizes these same LEDs, but not using LBS. LEDs turn on and off as expected.

Both application and network DTS files have the same LED assignments.

Suggestions?

[Stian Røed Hafskjold]

Hi, it the peripheral_lbs sample is using the dk_buttons_and_leds library which is setting the output of the GPIO based on the CONFIG_DK_LIBRARY_INVERT_LEDS config:

err = gpio_pin_set_raw(led_devs[led_idx], led_pins[led_idx].number, IS_ENABLED(CONFIG_DK_LIBRARY_INVERT_LEDS) ? !val : val);

https://github.com/nrfconnect/sdk-nrf/blob/41202f304f0e67423448afc5368fd4d640cb73e6/lib/dk_buttons_and_leds/dk_buttons_and_leds.c#L388

The config is set to =y by default, so changing this to =n should give you an active high output.

[brec]

Thanks Stian, That did the trick.

I placed CONFIG_DK_LIBRARY_INVERT_LEDS=n in the <boardname>_cpuapp_defconfig, <boardname>_cpuappns_defconfig, and <boardname>_cpunet_defconfig to cover all cases for this board.

Bob