Excluding 32MHz crystal and 32KHz crystal from nRF52 custom board.

RE: Excluding 32MHz crystal and 32KHz crystal from nRF52 custom board.

RK — Mon, 13 Feb 2017 12:12:07 GMT

well if you're using bluetooth then no you can't remove the 32MHz crystal because it's required for radio operation. You can remove the 32kHz crystal if you want. However as others have pointed out, your current consumption is higher than it should be for the peripherals you're using and so you are most likely looking in the wrong place.

RE: Excluding 32MHz crystal and 32KHz crystal from nRF52 custom board.

Keton — Mon, 13 Feb 2017 10:52:25 GMT

MPU9250 has typical power consumption of about 4mA. TWI master + connection application should draw no more than 1mA without too much power management. Optimized it should go down to about 0.5mA or even lower depending on how long TWI peripheral is active. So check your code.

RE: Excluding 32MHz crystal and 32KHz crystal from nRF52 custom board.

Swapnil — Mon, 13 Feb 2017 10:31:15 GMT

I am using nRF52 for reading data from MPU9250 using bluetooth application in mobile. And complete current consumption is 15mA.

RE: Excluding 32MHz crystal and 32KHz crystal from nRF52 custom board.

Keton — Mon, 13 Feb 2017 10:05:58 GMT

15mA is a lot for nRF5x application. Either you're using additional components that are power hungry or there's much to optimize in your code. Cutting out crystals most likely won't help you. They aren't running when they're not needed and I can easily achieve 40 uA in BLE connection with lots of processing going on and both crystals used.