nRF52832 current consumption in idle

RE: nRF52832 current consumption in idle

Kazi Afroza Sultana — Fri, 13 Oct 2023 12:13:59 GMT

Hello Mike,

Thanks for the explanation.

I can not see anything wrong in the code. Can you add the following configurations kconfig file and see if it works?

CONFIG_CONSOLE=y
CONFIG_UART_CONSOLE=y

RE: nRF52832 current consumption in idle

Mike Austin (LPI) — Sat, 07 Oct 2023 01:15:24 GMT

Hi Kazi,

Looks like you were right!

Changed my configuration for the LEDs to the following:

ret = gpio_pin_configure_dt(&led1, GPIO_OUTPUT | \
				 GPIO_OUTPUT_INIT_LOW |	\
				 GPIO_OUTPUT_INIT_LOGICAL | \
				 GPIO_OPEN_DRAIN);

And I'm now seeing the sort of current in idle mode that I was expecting (well, as far as I can tell from my CurrentRanger - the current is jumping around a bit). I might invest in a PPK 2 to get a better handle on what's truly going on.

The gpio_pin_set_dt(&led0,0) code is there just there to turn the LEDs off at the start of my code. I then toggle them in my button press callback. As I understand it, I'm using three different LEDs in my code - led0, led1 and led2. Am I missing something?

Still can't work out why the printk("Button x pressed\n") messages aren't getting printed to the terminal in my callback though. Are you able to see what I'm doing wrong?

Regards,

Mike

RE: nRF52832 current consumption in idle

Kazi Afroza Sultana — Fri, 06 Oct 2023 13:49:29 GMT

Hello Mike,

200uA sounds like the current flowing through our internal pull resistors if the state of the pin is opposite of the pull config (e.g. pullup + pin set to low). Can I look at your set up how you measured the current using CurrentRanger?

Can you please explain this part of the code

Did you mean to use same pin for 3 leds?

Thanks.

BR
kazi