lfclk, rtc issue on SDK13

RE: lfclk, rtc issue on SDK13

pirm — Tue, 07 Nov 2017 10:40:13 GMT

Thank you for your answer. While trying to purge my code to send the project, I found my mistake: I was declaring an instance of the RTC that was different from wich declared in sdk_config.h : const nrf_drv_rtc_t rtc = NRF_DRV_RTC_INSTANCE(0); /**< Declaring an instance of nrf_drv_rtc for RTC0. */

I change to RTC2 and it works. It was an heritage from previous work with SDK11 and nRF51822 board.

RE: lfclk, rtc issue on SDK13

Jørgen Holmefjord — Wed, 01 Nov 2017 11:24:31 GMT

Error 4097 (0x1001) corresponds to NRF_ERROR_SDM_INCORRECT_INTERRUPT_CONFIGURATION. The second error (INVALID MEMORY ACCESS) indicates that the function is accessing a peripheral restricted or blocked by the softdevice, without using the softdevice API. Can you upload the project for review of the code and debugging?

RE: lfclk, rtc issue on SDK13

pirm — Thu, 26 Oct 2017 16:49:47 GMT

I have the same problem with SDK 14.1. If I initialize CLOCK and RTC driver before BLE stack I have an error in return of nrf_sdh_enable_request():

<error> app: ERROR 4097 [Unknown error code]

If I initialize BLE stack first, I can initialize CLOCK (nrf_drv_clock_init()) but RTC initialization fails (nrf_drv_rtc_init()) with the error:

<error> app: SOFTDEVICE: INVALID MEMORY ACCESS

RTC section of sdk_config.h:

// <e> RTC_ENABLED - nrf_drv_rtc - RTC peripheral driver
//==========================================================
#ifndef RTC_ENABLED
#define RTC_ENABLED 1
#endif
// <o> RTC_DEFAULT_CONFIG_FREQUENCY - Frequency  <16-32768> 


#ifndef RTC_DEFAULT_CONFIG_FREQUENCY
#define RTC_DEFAULT_CONFIG_FREQUENCY 32768
#endif

// <q> RTC_DEFAULT_CONFIG_RELIABLE  - Ensures safe compare event triggering
 

#ifndef RTC_DEFAULT_CONFIG_RELIABLE
#define RTC_DEFAULT_CONFIG_RELIABLE 0
#endif

// <o> RTC_DEFAULT_CONFIG_IRQ_PRIORITY  - Interrupt priority
 

// <i> Priorities 0,2 (nRF51) and 0,1,4,5 (nRF52) are reserved for SoftDevice
// <0=> 0 (highest) 
// <1=> 1 
// <2=> 2 
// <3=> 3 
// <4=> 4 
// <5=> 5 
// <6=> 6 
// <7=> 7 

#ifndef RTC_DEFAULT_CONFIG_IRQ_PRIORITY
#define RTC_DEFAULT_CONFIG_IRQ_PRIORITY 7
#endif

// <q> RTC0_ENABLED  - Enable RTC0 instance
 

#ifndef RTC0_ENABLED
#define RTC0_ENABLED 0
#endif

// <q> RTC1_ENABLED  - Enable RTC1 instance
 

#ifndef RTC1_ENABLED
#define RTC1_ENABLED 0
#endif

// <q> RTC2_ENABLED  - Enable RTC2 instance
 

#ifndef RTC2_ENABLED
#define RTC2_ENABLED 1
#endif

// <o> NRF_MAXIMUM_LATENCY_US - Maximum possible time[us] in highest priority interrupt 
#ifndef NRF_MAXIMUM_LATENCY_US
#define NRF_MAXIMUM_LATENCY_US 2000
#endif

RE: lfclk, rtc issue on SDK13

fteng — Tue, 01 Aug 2017 22:02:24 GMT

After some debugging I come to the conclusion there is a condition check in sd_softdevice_enable on lfclk that does not allow lfclk to be enabled outside of softdevice. It raises an exception if so.

RE: lfclk, rtc issue on SDK13

Jørgen Holmefjord — Fri, 28 Jul 2017 08:41:07 GMT

Hi,

You can't call nrf_drv_rtc_init() with p_config = NULL. There is an assert inside the function that checks if p_config is set, but this is not firing for some reason. If called without config, the priority will not be set to one of the allowed levels for use with softdevice.

You should get default config from sdk_config.h like this:

static void rtc_config(void)
{
    uint32_t err_code;

    //Initialize RTC instance
    nrf_drv_rtc_config_t config = NRF_DRV_RTC_DEFAULT_CONFIG;
    err_code = nrf_drv_rtc_init(&rtc, &config, rtc_handler);
    APP_ERROR_CHECK(err_code);
}

Best regards,

Jørgen

RE: lfclk, rtc issue on SDK13

fteng — Thu, 27 Jul 2017 22:47:25 GMT

const nrf_drv_rtc_t rtc = NRF_DRV_RTC_INSTANCE(2); sdk_config.h probably too large to upload. I just change the followings in a ble_app_hrs or ble_app_hts example. everything else stays the same except lfclk_config(), rtc_config(void) added.

#define CLOCK_ENABLED 1
#define RTC_ENABLED 1
#define RTC2_ENABLED 1

RE: lfclk, rtc issue on SDK13

Jørgen Holmefjord — Thu, 27 Jul 2017 08:13:05 GMT

Could you upload your sdk_config.h file, and the declaration of the RTC instance, rtc (used in nrf_drv_rtc_init())?

RE: lfclk, rtc issue on SDK13

fteng — Wed, 26 Jul 2017 20:11:12 GMT

Thx, Jørgen. I used the method to check the error code. It is 0x1001 = NRF_ERROR_SDM_INCORRECT_INTERRUPT_CONFIGURATION in function ble_stack_init() --> SOFTDEVICE_HANDLER_INIT(&clock_lf_cfg, NULL); clock_lf_cfg is from NRF_CLOCK_LFCLKSRC -- default setting in pca10040.h I develop this on an nRF52 base Murata (which I work for) module and I have to port the project to eclipse/GCC due to code size limit in Keil. It doesn't look like a hardware or toolchain issue to me though, since SDK11 works fine on the same platform. Seems like softdevice in SDK13 takes over RTC and application can't access it anymore.

RE: lfclk, rtc issue on SDK13

Jørgen Holmefjord — Tue, 25 Jul 2017 13:08:11 GMT

Have you tried checking for error codes using this method? Aslo, what is your LFCLK settings? Are you testing this on the nRF52 DK or a custom board?

RE: lfclk, rtc issue on SDK13

fteng — Mon, 24 Jul 2017 22:45:49 GMT

Here I ported it to the ble_app_hts_c project in Nordic example codes. lfclk_config() and rtc_config() are the two functions added. It is going to crash in ble_stack_init() in the following order. If I put the two clock functions after ble_stack_init(), they failed. Looks the three functions are fighting each other. It works fine in SDK11 though.

int main(void)
{
...
lfclk_config();                                  //Configure low frequency 32kHz clock
rtc_config();                                    //Configure RTC. 
APP_TIMER_INIT(APP_TIMER_PRESCALER, APP_TIMER_OP_QUEUE_SIZE, NULL);
buttons_leds_init(&erase_bonds);
nrf_log_init();
APPL_LOG("Temperature collector example\r\n");
ble_stack_init();
...
}
static void lfclk_config(void)
{
    ret_code_t err_code = nrf_drv_clock_init();                        //Initialize the clock source specified in the nrf_drv_config.h file, i.e. the CLOCK_CONFIG_LF_SRC constant
    APP_ERROR_CHECK(err_code);

    nrf_drv_clock_lfclk_request(NULL);
}

static void rtc_config(void)
{
    uint32_t err_code;

    //Initialize RTC instance
    err_code = nrf_drv_rtc_init(&rtc, NULL, rtc_handler);              //Initialize the RTC with callback function rtc_handler. The rtc_handler must be implemented in this applicaiton. Passing NULL here for RTC configuration means that configuration will be taken from the nrf_drv_config.h file.
    APP_ERROR_CHECK(err_code);

    err_code = nrf_drv_rtc_cc_set(&rtc,0,RTC_CC_VALUE,true);           //Set RTC compare value to trigger interrupt. Configure the interrupt frequency by adjust RTC_CC_VALUE and RTC2_CONFIG_FREQUENCY constant in the nrf_drv_config.h file
    APP_ERROR_CHECK(err_code);

    //Power on RTC instance
    nrf_drv_rtc_enable(&rtc);                                          //Enable RTC
}

RE: lfclk, rtc issue on SDK13

Jørgen Holmefjord — Fri, 21 Jul 2017 08:26:42 GMT

Could you describe the conflicts and problems in more detail? And provide some code snippets showing setup/configuration? I'm not aware of any major changes in these modules.