Large current drain with EVENTS_IN enable via high_accuracy flag

Hi,

I need to enable an input interrupt on nRF52832 and I want to use a GPIOTE EVENTS_IN channel.

During boot configuration, I'm using nrfx_gpiote_in_init function with the hi_accuracy flag = 1, since only with this flag enabled a GPIOTE channel from 0 to 7 is assigned to pin by nrfx_gpiote_in_init (instead of the PORT EVENT in position 8 when hi_accuracy = 0 ).

The problem is that: when I enable the EVENTS_IN channel on the rising edge of the assigned input pin in this way, current drain increases a lot (more or less 200 uA), but I need to avoid this large current consumption for project requirements.

Is there any reason why this great current drain in this condition? Is a PULL enabled into nrfx_gpiote_in_init? How can I use a GPIOTE EVENTS_IN channel maintaining low current drain?

Parents
  • Hello Alex,
    Not sure how you have configured the clock source used, but based on what you are seeing in current consumption, I suspect the you might have HFXO running or enabled. You can configure to use the HFINT instead and it will drop down to 60uA with the SENSE functionality.
    If not clock source, how have you configured the pins in play. Any chance that it might be configure to source current and the other side sink it?
    Best regards
    Asbjørn
Reply
  • Hello Alex,
    Not sure how you have configured the clock source used, but based on what you are seeing in current consumption, I suspect the you might have HFXO running or enabled. You can configure to use the HFINT instead and it will drop down to 60uA with the SENSE functionality.
    If not clock source, how have you configured the pins in play. Any chance that it might be configure to source current and the other side sink it?
    Best regards
    Asbjørn
Children
No Data
Related