npm1300 interrupts

RE: npm1300 interrupts

Thimen — Wed, 23 Apr 2025 16:22:04 GMT

The idea is that the GPIO line acts like a more generic "interrupt alert" signal, and then your host MCU can query the NPM1300's internal status registers (like EVENTS or geometry vibes) via I2C to figure out exactly what triggered it—whether it was a state of charge, low voltage, or some error condition.

RE: npm1300 interrupts

GraceMansfield — Tue, 15 Apr 2025 09:22:14 GMT

@sprunki phase 3, Thank you so much for taking the time to share this detailed and useful information. Your sharing really helped me understand better how to handle events and interrupts in the application and saved a lot of time during development.

RE: npm1300 interrupts

Andy Sinclair — Mon, 05 Aug 2024 09:31:29 GMT

Yes, any GPIO mode can be used as an interrupt output (set GPIOMODE to GPOIRQ).

Watchdog warning generates an event (EVENTWATCHDOGWARN) which will assert this pin if enabled.

RE: npm1300 interrupts

dave — Sun, 04 Aug 2024 02:23:50 GMT

Thanks... Can you clarify if I can select which pin the events are routed to?

Is the watchdog timer about to expire interrupt in the same event group?

RE: npm1300 interrupts

Andy Sinclair — Fri, 02 Aug 2024 07:50:22 GMT

Hi.

All events share a single interrupt, the host needs to check the event registers to see the cause of the interrupt.
Please see this sample for an example:
sdk-nrf/samples/pmic/native/npm1300_one_button/src/main.c at main · nrfconnect/sdk-nrf (github.com)

It's not possible to route particular events to a different pin.

Andy