nrf_sdh_enable_request takes quite a long time to end (S132 6.1.1)

RE: nrf_sdh_enable_request takes quite a long time to end (S132 6.1.1)

Aurele — Wed, 18 Dec 2019 10:32:47 GMT

Maybe someone from the Nordic team could be more useful than me for this issue, im sorry i dont have any clue

RE: nrf_sdh_enable_request takes quite a long time to end (S132 6.1.1)

Sridhar Jonnavittula — Tue, 17 Dec 2019 11:26:52 GMT

Hi,

Even though I replaced clock sources, it is taking ~50ms for ble_stack_init to complete.

RE: nrf_sdh_enable_request takes quite a long time to end (S132 6.1.1)

Aurele — Tue, 17 Dec 2019 10:39:21 GMT

Hello,

Here is my sdk_config, but actually it is the one from the project example.

devzone.nordicsemi.com/.../6746.sdk_5F00_config.h

My definitions are made in the app_config.h file that is included by sdk_config :

#define NRF_BLE_QWR_ENABLED                   0
#define NRF_BLE_SCAN_SCAN_DURATION            400
#define NRF_BLE_SCAN_SCAN_WINDOW              160
#define BLE_NUS_C_ENABLED                     1
#define BLE_NUS_ENABLED                       1
#define NRFX_CLOCK_CONFIG_LF_SRC              0
#define NRFX_RTC_DEFAULT_CONFIG_IRQ_PRIORITY  7
#define NRFX_WDT_CONFIG_BEHAVIOUR             0 // wdt pause in SLEEP and HALT 
#define NRFX_WDT_CONFIG_RELOAD_VALUE          40000
#define CLOCK_CONFIG_LF_SRC                   0 // RC oscillator
#define SAADC_ENABLED                         1
#define SAADC_CONFIG_RESOLUTION               2
#define SAADC_CONFIG_LP_MODE                  1
#define SAADC_CONFIG_IRQ_PRIORITY             7
#define TWI_ENABLED                           1
#define TWI_DEFAULT_CONFIG_FREQUENCY          104857600
#define TWI_DEFAULT_CONFIG_HOLD_BUS_UNINIT    1
#define TWI_DEFAULT_CONFIG_IRQ_PRIORITY       7
#define TWI0_ENABLED                          1
#define WDT_ENABLED                           1
#define WDT_CONFIG_BEHAVIOUR                  0
#define WDT_CONFIG_RELOAD_VALUE               40000
#define APP_SCHEDULER_ENABLED                 0
#define APP_TIMER_CONFIG_RTC_FREQUENCY        0
#define LOW_POWER_PWM_ENABLED                 1
#define NRF_SORTLIST_ENABLED                  0
#define NRF_LOG_BACKEND_RTT_ENABLED           1
#define NRF_LOG_BACKEND_RTT_TEMP_BUFFER_SIZE  128
#define NRF_LOG_BACKEND_UART_ENABLED          0
#define NRF_SDH_BLE_TOTAL_LINK_COUNT          2
#define NRF_SDH_BLE_GAP_EVENT_LENGTH          10
#define NRF_SDH_BLE_GATT_MAX_MTU_SIZE         32
#define NRF_SDH_BLE_VS_UUID_COUNT             1
#define NRF_SDH_DISPATCH_MODEL                2
#define NRF_SDH_CLOCK_LF_SRC                  0
#define NRF_SDH_CLOCK_LF_RC_CTIV              31
#define NRF_SDH_CLOCK_LF_RC_TEMP_CTIV         31
#define NRF_SDH_CLOCK_LF_ACCURACY             1
#define FDS_VIRTUAL_PAGES                     3     // Total size of FDS : 3*1024*4 = 12kB

#define PPI_ENABLED                           1
#define GPIOTE_ENABLED                        1
#define GPIOTE_CONFIG_NUM_OF_LOW_POWER_EVENTS 1

#define APP_UART_ENABLED                      0
#define RETARGET_ENABLED                      0

#define RTC_ENABLED                           1
#define RTC2_ENABLED                          1

I think your issue could come from the LF clock source or RTC source.

Regards,

Aurélien

RE: nrf_sdh_enable_request takes quite a long time to end (S132 6.1.1)

Sridhar Jonnavittula — Tue, 17 Dec 2019 09:42:07 GMT

Hi Aurel,

I am also facing same issue. Could you please attach the sdk_config file?

Also please tell me what is the amount of value decreased from 2sec?

Thanks

Sridhar

RE: nrf_sdh_enable_request takes quite a long time to end (S132 6.1.1)

Aurele — Wed, 23 Oct 2019 08:41:04 GMT

Hello,

I can share you my sdk_config file if you want because i don't remember exactly the modifications i have made :)

Regards

RE: nrf_sdh_enable_request takes quite a long time to end (S132 6.1.1)

gercer — Fri, 18 Oct 2019 20:36:07 GMT

im having the same issue could you let me know where what you had to change?

RE: nrf_sdh_enable_request takes quite a long time to end (S132 6.1.1)

Aurele — Tue, 07 May 2019 09:51:43 GMT

Finally, it's ok, i found the issue. There was a missing configuration about clock in my sdk config file.

Regards,