I'm developing a beacon application using the Fanstel BT832AF, which uses the nRF52810 internally. This unit is mounted to a custom board, but before raising a private ticket I wanted to see if the community had seen similar.
Using the PPK-II's Ampere Meter, I'm seeing a very high current consumption with SystemOn sleep, ~350uA when I'm to understand it should be around 1.9uA. I've followed the recommendations here and also for the nRF51.
In terms of hardware, I've been able to remove all the other devices from the PCBA so am just testing the BT832AF (nRF52810) in isolation, which makes this high current value more peculiar. The custom board has a 32.768kHz XTAL, which the module makes use of and the nRF is configured to use that XTAL as the LFOSC input. Power is supplied to the board using a CR2477 coin cell at 3V and the DCDC regulator is supported in hardware in the BT832 module.
For software, I'm using SDK17.0.2 and have created a bare minimum beacon project from the BLE Beacon PCA10040e example, adapting it for the board. I've been able to verify the system is sleeping, as the consumption when active is around 3mA. The only peripherals enabled in sdk_config.h are TWI and the SAADC, but neither are actually enabled. The common culprits- UART and Logging have been disabled from the config. The DCDC is enabled through software.
The main of my project is as follows:
int main(void)
{
ret_code_t err_code;
// Initialize.
twi_init(); // but not enabled
timers_init();
power_management_init();
ble_stack_init();
my_timer_init(); // creates app timer but not started
sd_power_dcdc_mode_set(NRF_POWER_DCDC_ENABLE);
sd_power_mode_set(NRF_POWER_MODE_LOWPWR);
// Enter main loop.
for (;; )
{
idle_state_handle();
}
}
Since it is just initializations with no peripherals enabled and then immediately into sleep, I'm not sure what else could be causing such high consumption. What else could be contributing?
