Please note that there is no issue with the current consumption when you use new component. Please ensure that you have followed the firmware flow mentioned in the project attached with the application note AN92584 - Designing for Low Power and Estimating Battery Life for BLE Applications.
The issue is premature battery failure along with resetting using CYBLE-012011-00.
Can you please elaborate more about the issue? What is the current consumed by your present project (after updating the BLE component)?
What do you mean by battery failure? Does that mean the battery is getting discharged quickly?
The current profile and the average current draw is roughly 2.9uA
Is this value is the current consumption before updating the BLE component?
Can you please attach your project once to check once at our side?
1 of 1 people found this helpful
This is almost certainly that your firmware doesn't deep sleep ... and that you are remaining in sleep or active.
These are a serious pain to debug... but you need to make sure that the chip is deep sleeping.
I have typically used a pin and an oscilloscope to look at the duty cycle of deep sleep.. write it before deep sleep and invert it when you come out... .and what I typically find is that something unexpected in system is causing unexpected by me wake ups.