working with s132 and app_timer but timing is not always good

RE: working with s132 and app_timer but timing is not always good

Vidar Berg — Thu, 03 Sep 2020 05:50:06 GMT

Hi Ziv,

Yes, NRF_SDH_CLOCK_LF_SRC=0 selects the internal RC oscillator. With this clock source you also need use the following settings:

- NRF_SDH_CLOCK_LF_RC_CTIV=16

- NRF_SDH_CLOCK_LF_RC_TEMP_CTIV=2

- NRF_SDH_CLOCK_LF_ACCURACY=1

RE: working with s132 and app_timer but timing is not always good

ziv123 — Wed, 02 Sep 2020 12:34:33 GMT

hi Vidar

1. the NRF_SDH_CLOCK_LF_SRC is set to -> 0 (if i understand correct it means i am using the nrf52832's LFCLK)

and also on the same board i run another app that also had s132 and app_timer and i did not need to add this lines of code (maybe it is done by some other module )

2. no there is no other change for the ble pin in the code

best regards

Ziv

RE: working with s132 and app_timer but timing is not always good

Vidar Berg — Wed, 02 Sep 2020 12:16:09 GMT

Hello,

1. As you say, it shouldn't be necessary to activate the LFCLK as the Softdevice should do that already. Are you testing this on a custom or third-party board? In that case, make sure you have selected an appropriate clock source in sdk_config.h (see NRF_SDH_CLOCK_LF_SRC). Not all boards have the optional 32 KHz crystal mounted.

2. Is there anything else in your application that might try to control the same LED? The BSP maybe (BSP indication states)?

3. Scanning will be active 100% of the time if you set SCAN_WINDOW=SCAN_INTERVAL

Best regards,

Vidar