Clock config of the MESH sdk 1.0

RE: Clock config of the MESH sdk 1.0

Beike — Thu, 25 Jan 2018 01:43:59 GMT

yes, you are right. Just doing this change is still working.

config_params.lf_clk_cfg.source = NRF_CLOCK_LF_SRC_RC;
config_params.lf_clk_cfg.accuracy = NRF_CLOCK_LF_ACCURACY_20_PPM;
config_params.lf_clk_cfg.rc_ctiv = 16;
config_params.lf_clk_cfg.rc_temp_ctiv = 2;

Thanks for your answer.

RE: Clock config of the MESH sdk 1.0

Hung Bui — Wed, 24 Jan 2018 15:47:38 GMT

According to this case, you should stil be able to configure with RC oscillator without using NULL as the lfc_cfg. Make sure you also configure the rc_ctiv and rc_temp_ctiv.

RE: Clock config of the MESH sdk 1.0

Beike — Wed, 24 Jan 2018 02:45:12 GMT

I has solved this problem.

I find this in the server project:

 * @param p_clock_lf_cfg Low frequency clock source and accuracy.
   If NULL the clock will be configured as an RC source with rc_ctiv = 16 and .rc_temp_ctiv = 2
   In the case of XTAL source, the PPM accuracy of the chosen clock source must be greater than 
   or equal to the actual characteristics of your XTAL clock.
 * @param fault_handler Callback to be invoked in case of fault, cannot be NULL.

so I do this changes in this fountion:

uint32_t softdevice_setup(nrf_clock_lf_cfg_t lfc_cfg, nrf_fault_handler_t assertion_handler)
{
    #if !defined(HOST)
    if (assertion_handler == NULL)
    {
        assertion_handler = default_softdevice_assertion_handler;
    }

    #if defined(S110)
        RETURN_ON_ERROR(sd_softdevice_enable(lfc_cfg, assertion_handler));
    #else
    // RETURN_ON_ERROR(sd_softdevice_enable(&lfc_cfg, assertion_handler));
        RETURN_ON_ERROR(sd_softdevice_enable(NULL, assertion_handler));
    #endif
        RETURN_ON_ERROR(sd_nvic_EnableIRQ(SD_EVT_IRQn));
    #endif

    return NRF_SUCCESS;
}

so, this project has run as respected.