PM3 state transition

Hi Evgeny,

You are correct, make sure that there is no Application activity and the device is not connected. The device should then go into PM3 automatically.

Br 

Thank you for reply.

Can I check somehow that it is really PM3?

Say, watch some variable through debugger? Or through other means?

BR,

Evgeny.

You can check it, for example, by measuring current consumption :)

http://www.ti.com/lit/an/swra347a/swra347a.pdf

Yes, I had it in mind ) but

ubfortunately we've got many periferial sensor on our device,

so not only chip consumes power and it's hard to guess actual state by current..

would be great to douvle check by some other means.. if it's posseble

BR,

Evgeny

Unfortunately in debug mode, the device cannot be in lower power modes. i.e when it is connected to the CC Debugger or SmartRF Studio the device cannot enter sleep mode, hence it would be difficult to read out whether the device is in PM3. Unfortunately the best way here would be to measure the current in the different modes to determine the state

Hi,

Back to the PM3 transition I explicitly switched off all timers in application (no activity)

and the device is not in connection but judging by oscillograph 32KHz clock still running - so presumably it is in PM2.

Should I correct something in BLE stack source files? hal_sleep.c or smth.?

Thank you.

BR,

Evgeny