Unable to read gpios

RE: Unable to read gpios

mwu — Tue, 02 Jun 2026 16:20:56 GMT

I ended up getting my smaller test project working and from there I simplified my main firmware project until the gpio reads worked. That narrowed me down to the problem which was my initialization of the RTC.

I ended up switching from using NRFX's RTC driver to using Zephyr's Counter driver. That resolved my issues.

RE: Unable to read gpios

mwu — Mon, 01 Jun 2026 23:11:48 GMT

I managed to set up an oscilloscope and connect it to my board. Here is what I'm seeing. The first screenshot is a button not pressed. The second is a button pressed.

Should I not see a steady high signal on a pin configured for pull up, active low and then a steady low signal when the button is pressed?

They both have about the same frequency with a period of about 18ms.

Any ideas what would cause this?

RE: Unable to read gpios

mwu — Fri, 22 May 2026 14:00:05 GMT

If I switch to gpio_port_get_raw(), the equivalent of my input mask is returned. When I use a multimeter I see ~3.3v (as expected since I'm using pull up, sense low).

edited for grammar (removed extra word)

RE: Unable to read gpios

Sigurd — Fri, 22 May 2026 13:49:09 GMT

Do you see the same with gpio_port_get_raw()?

Have you tried measuring the GPIOs externally with a multimeter? are they actually 0V?

RE: Unable to read gpios

mwu — Thu, 21 May 2026 12:12:59 GMT

There is also a board definition in the leaf-fall firmware directory for the Raytac module that I created and tried using which doesn't define as many unused things on the device tree as the nrf52dk does. It has the same issues when using either DTS.