Hi All,
We are currently working on current optimization for the KW45 on our custom-designed PCB and have encountered an unusual issue. The scan parameters we have configured are as follows:
gapScanningParameters_t gScanParams =
{
/* type */ gScanTypePassive_c,
/* interval */ 4000, /* Interval * 0.625 = scan interval in ms */
/* window */ 650,
/* ownAddressType */ gBleAddrTypePublic_c,
/* filterPolicy */ (uint8_t)gScanAll_c,
/* scanning PHY */ (uint8_t)gLePhy1MFlag_c
};
appScanningParams_t appScanParams = {
&gScanParams,
gGapDuplicateFilteringDisable_c,
1500,
gGapScanPeriodicDisabled_d
};
Here’s the behavior we observe:
- When scanning is disabled, the current consumption is approximately 0.70 mA, which is expected.
- When scanning is enabled, the expected current consumption should vary between 0.70 mA and 6.75 mA, as scanning is not continuous.
- However, we observe that the current consumption gets stuck at 2.99 mA for a while before eventually dropping to 0.70 mA.
It seems that the KW45 is unable to enter low-power mode consistently during scanning.
Notably, this issue only began after porting our code to the SDK_2.x_KW45b41z83xxxA_2.12.7.
Previously, under the older SDK version (2.12.2), the current consumption was working as expected.
Could you please help us identify the root cause of the unexpected 2.99 mA current consumption?
Any insights or suggestions for debugging this issue would be greatly appreciated.
KW45 BLE-NFC
Regards
Shivam
