SAADC always busy

RE: SAADC always busy

dblasco — Fri, 21 Apr 2017 09:39:21 GMT

Right, sorry I never inquired further. Thank you.

RE: SAADC always busy

Jørgen Holmefjord — Fri, 21 Apr 2017 09:37:36 GMT

Yes, you need to use one of the supported softdevices. From release notes:

Supported SoftDevices:

S132 v4.0.2

S140 v5.0.0-2.alpha

S212 v4.0.0

RE: SAADC always busy

dblasco — Fri, 21 Apr 2017 09:35:28 GMT

I got error 0x3001 in sd_ble_cfg_set. I have not made any modification to this SDK 13.0.0 (downloaded yesterday) Softdevice used was s132 v3.0.1 (the same as with SDK12). Maybe should I have used 4.0.2?

RE: SAADC always busy

Jørgen Holmefjord — Fri, 21 Apr 2017 09:26:26 GMT

Great that you got it working! Which error do you get from ble_stack_init? Have you flashed the correct softdevice? Have you made any other changes to the SDK? I tried the Eddystone example from SDK 13 on my board, and it seems to work as expected.

RE: SAADC always busy

dblasco — Fri, 21 Apr 2017 08:37:37 GMT

Hi Jørgen. I have updated SAADC driver and the part related to the battery measurement of eddystone example to SDK13. It works now (however, the whole eddystone example in SDK 13 does not work, gives an error in ble_stack_init, in case you wanted to check). Thank you for your help. I

RE: SAADC always busy

Jørgen Holmefjord — Thu, 20 Apr 2017 14:45:15 GMT

Hi,

There are some issues with low-power mode in SDK 12.x. These should be fixed in SDK 13. Where do the sampling stop? Do you get an error code from any calls to driver functions?

Are you using double buffering in your application? The SAADC will be kept in the busy-state as long as there are a second buffer setup for sampling. This is also causing some issues for users trying to run the calibration task, as described in this post.

Best regards,

Jørgen