Current consumption ble

[lydie]

Hi,

I'm using nrf52832 with s132, so I don't find any information about the current consumed by the device when I'm connected by Bluetooth. I use the driver st7735 and an LCD screen. When my phone is not connected by Bluetooth and my device sleep, the current is 0.43mA. When my phone is not connected, and the LCD screen is ON, the current is around 3.4mA. Until then, everything is normal. But when I'm connected and my device is sleeping, the current is 1.5mA, and if the screen is ON the current is 0.7mA. So I don't understand why the current is increased when I'm connected and when my device is sleeping? And why the current decrease when the screen displays something. On online power profiler, the power consumes when there is a connection but the device is asleep is not indicated, so I don't know if it is normal or not. 

Thanks,

Lydie

[bjorn-spockeli]

Ok, so you are using the UART to print log statements? By EVENTS_xxxx I mean the EVENTS registers for each of the peripherals, e.g. the UART event registers listed here: UART Registers

EVENTS_CTS	0x100	CTS is activated (set low). Clear To Send.
EVENTS_NCTS	0x104	CTS is deactivated (set high). Not Clear To Send.
EVENTS_RXDRDY	0x108	Data received in RXD
EVENTS_TXDRDY	0x11C	Data sent from TXD
EVENTS_ERROR	0x124	Error detected
EVENTS_RXTO	0x144	Receiver timeout

If any of these registers are set to 1, i.e. there is a pending event, then sd_app_evt_wait will return immediatly.

Best regards

Bjørn

[lydie]

Yes! Ok, and how can I know if any of EVENTS_xxxx are set to 1?

[bjorn-spockeli]

Well, you could print the values with the UART interface or monitor the registers of the peripherals in debug session.

[lydie]

Yes, but where? I printed in all handler function of each service, but no events are called. 

[bjorn-spockeli]

Hi lydie, 

Sorry for not explaining this better. I would check the EVENTS_ registers just before  sd_app_evt_wait() is called in nrf_pwr_mgmt_run(). As I tried to explain in my previous comments, any pending events, i.e. if any EVENTS_ register for any peripheral isnt cleared prior to calling sd_app_evt_wait(), then sd_app_evt_wait() will return immediatly. 

Hence I would start looking at the EVENTS regisiters of the peripherals that you are using your application, e.g. UART and SPI . 

Best regards

Bjørn