Why doesn't the SDK expose POFCON values for 2.0V, 1.9V, 1.8V or 1.7V?

[jprofit]

I would like to use the POFCON register thresholds to create a crude battery level indicator. I noticed that the POFCON register definition in the nRF52832 Product Spec has threshold values for 1.7V, 1.8V, 1.9V, 2.0V, 2.1V, 2.2V ... 2.8V. Unfortunately, the SDK only exposes 2.1V, 2.3V, 2.5V and 2.7V.

Is there some reason why the SDK hides the other values? If my firmware programs the POFCON register directly, how can I avoid conflicts with the SDK's use of that register?

Jack

[Ole Bauck]

The problem is with the SoftDevice which only takes the values from nRF51 (2.1V, 2.3V, 2.5V and 2.7V), see here. I have reported this internally and we will work on it.

I would however recommend to use the SAADC instead to measure battery voltage. See for example the ble_app_hrs example which uses the battery service (bas).

[annapalu]

Hi all,

but if i would use the threshold different from enum (1.9 V), I repeat the question of Jack " If my firmware programs the POFCON register directly, how can I avoid conflicts with the SDK's use of that register?"

Or better if i set the register directly can be a issue with sdk?