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.
I think when my phone is connected to my device, it can't enter in a sleeping mode, that's why the current is always around 1.5mA. So my question is how enter the device I sleeping mode when my phone is connected?
which S132 version and SDK version are you using?
All the BLE examples in our nRF5 SDK will go to sleep when the CPU is idling, i.e. in between connection events and advertisment events. Our SoftDevice is 100% event driven so, whenever the nRF is in the main for() loop it will call idle_state_handle(), which in turn calls nrf_pwr_mgmt_run(), which in turn calls sd_app_evt_wait() or __WFE(). These functions will make the CPU sleep until there is an interrupt or event that wakes up the chip, i.e. a timer expiring or a BLE event like advertisment or a connection event. So as long as you're calling idle_state_handle() in the main for loop, the nRF should go to sleep in between connection events.
// Wait for an event.
ret_code_t ret_code = sd_app_evt_wait();
ASSERT((ret_code == NRF_SUCCESS) || (ret_code == NRF_ERROR_SOFTDEVICE_NOT_ENABLED));
#endif // SOFTDEVICE_PRESENT
// Wait for an event.
// Clear the internal event register.
static void idle_state_handle(void)
if (NRF_LOG_PROCESS() == false)
/**@brief Function for application main entry.
// Start execution.
NRF_LOG_INFO("Blinky example started.");
// Enter main loop.
If its not going to sleep, then there must be a pending event/interrupt that keeps the CPU from sleeping, i.e. causes sd_app_evt_wait() or __WFE() to return immediately.
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.
The online power profiler will calculate the average current consumption with the assumption that the CPU goes to sleep inbetween connection and/or advertisment events.
I'm using sdk15.3. Ok I understand, so to decrease the current, I have to find which event or advertisement prevent the CPU from sleeping. But I haven't found any events. I tried with cts example, but the current neved decreases when I'm connected.
Thanks for your reply.
How are you measuring the current consumption, i.e. setup? What type of measurement hardware are you using?
lydie said: I tried with cts example, but the current neved decreases when I'm connected.
The default CTS example, i.e. nRF5_SDK_15.3.0_59ac345\examples\ble_peripheral\ble_app_cts_c ? No changes made?
I'm using a serial amperemeter. + is connected to my gbf, and the com VDD of my device. Yes CTS example and I haven't made any changes.