POFCON and s132

RE: POFCON and s132

annapalu — Wed, 13 Sep 2017 14:43:47 GMT

Thank you ambystomaLabs, your answer was very useful.

-Anna

RE: POFCON and s132

AmbystomaLabs — Wed, 13 Sep 2017 13:02:07 GMT

In theory 2.0.1 only has bug fixes. API implementations are supposed to be the same. So, you should be able to use 2.0.1 without changes. Also, one fix that might be of interest had to do with power consumption. So, you should consider just moving to 2.0.1.

Plus the fix of writing to the register directly for 2.0 was difficult since you can't then alter POF after you enable the SD. This was a problem for us since I wanted a two tiered approach to low battery detection. Ultimately I ended up using the ADC on an hourly basis to monitor the battery level.

RE: POFCON and s132

annapalu — Wed, 13 Sep 2017 12:25:21 GMT

Hy Amby thank you for your answer. I have tried and it set correctly the register.

So my questions is: Change the softdevice 2.0.1 have a impact on other function or is better set the register manually? What is your opinion?

Thanks, Anna

RE: POFCON and s132

AmbystomaLabs — Wed, 13 Sep 2017 11:58:33 GMT

This was fixed in S132 2.0.1. Though I haven't tried out the fixed version since we moved away from using the POF. However, if you haven't migrated to the latest SD and are still using 2.0 APIs, then 2.0.1 should solve your problem.

RE: POFCON and s132

annapalu — Wed, 13 Sep 2017 08:45:19 GMT

Hi, i have the same problem. If i use sd_power_pof_threshold_set(NRF_POWER_THRESHOLD_V27) the register NRF_POWER->POFCON is set equal to 7, and so it don't wotk correctly. If i try to set register directly have a reset from softdevice.

How do you have solve the problem?

RE: POFCON and s132

AmbystomaLabs — Tue, 15 Mar 2016 19:15:24 GMT

Many thanks for the quick response. I will make it a point to look at fixing the enumerations before writing to the register directly.

RE: POFCON and s132

Ole Bauck — Wed, 09 Mar 2016 15:27:26 GMT

This is probably just ported from the nRF51. I will report this internally. Generally you should not use the NRF_POWER register directly as it is restricted by the SoftDevice, see here.

RE: POFCON and s132

AmbystomaLabs — Wed, 09 Mar 2016 14:28:22 GMT

We figured this out in the debugger. There is something wrong with the enumerations in the 11.0.0.2 sdk. Using sd_power_pof_threshold_set(NRF_POWER_THRESHOLD_V23) will result in a value of 3 in the threshold register which is undefined. What works is to just set POFCON directly. Use: NRF_POWER->POFCON = 0X15; This will turn on pof and set threshold to 2.3 volts in one line. You can figure out from the reference manual how to set other thresholds. Someone should double check the enumerations in the nRF52 reference manual and the sample code.