nrf5-calendar-example SOFTDEVICE: INVALID MEMORY ACCESS

RE: nrf5-calendar-example SOFTDEVICE: INVALID MEMORY ACCESS

snowuyl — Wed, 29 Jun 2022 01:30:29 GMT

Thanks for your great support! Time is correct after changing nrf_cal_set_time() as follows.

void nrf_cal_set_time(uint32_t year, uint32_t month, uint32_t day, uint32_t hour, uint32_t minute, uint32_t second) {
    NRF_LOG_DEBUG("nrf_cal_set_time(%u, %u, %u, %u, %u, %u) e\n", year, month, day, hour, minute, second);
    static time_t uncal_difftime, difftime, newtime;
    time_struct.tm_year = year - 1900;
    time_struct.tm_mon = month - 1;
    time_struct.tm_mday = day;
    time_struct.tm_hour = hour;
    time_struct.tm_min = minute;
    time_struct.tm_sec = second;
    newtime = mktime(&time_struct);

    CAL_RTC->TASKS_CLEAR = 1;

    // Calculate the calibration offset
    if (m_last_calibrate_time != 0) {
        difftime = newtime - m_last_calibrate_time;
        uncal_difftime = m_time - m_last_calibrate_time;
        m_calibrate_factor = (float)difftime / (float)uncal_difftime;
    }

    // Assign the new time to the local time variables
    m_time = m_last_calibrate_time = newtime;
    //_nrf_cal_print_time_t(newtime);
    gCalTimeSet = true;
    NRF_LOG_DEBUG("nrf_cal_set_time(%u, %u, %u, %u, %u, %u) x\n", year, month, day, hour, minute, second);
}

Log messages.

<debug> app: nrf_cal_set_time(2022, 6, 29, 9, 24, 49) x
0>
0> <info> app:
0>
0> <debug> app: Uncalibrated time: 06/29/22 - 09:24:49
0>
0> <debug> app: Calibrated time: 06/29/22 - 09:24:49

RE: nrf5-calendar-example SOFTDEVICE: INVALID MEMORY ACCESS

Vidar Berg — Tue, 28 Jun 2022 10:45:34 GMT

The month is off by one because time.h counts the first month from zero.

RE: nrf5-calendar-example SOFTDEVICE: INVALID MEMORY ACCESS

snowuyl — Tue, 28 Jun 2022 10:06:36 GMT

After I modified nrf_cal_init() as follows. Time is almost correct except month.

void nrf_cal_init(void) {
    gCalTimeSet          = false;
   // Configure the RTC for 1 minute wakeup (default)
    CAL_RTC->PRESCALER   = 0xFFF;
    CAL_RTC->EVTENSET    = RTC_EVTENSET_COMPARE0_Msk;
    CAL_RTC->INTENSET    = RTC_INTENSET_COMPARE0_Msk;
    CAL_RTC->CC[0]       = m_rtc_increment * 8;
    CAL_RTC->TASKS_START = 1;
    NVIC_SetPriority(CAL_RTC_IRQn, CAL_RTC_IRQ_Priority);
    NVIC_EnableIRQ(CAL_RTC_IRQn);
    nrf_cal_set_callback(nrf_cal_updated, 4);
}

Log messages.

<debug> app: nrf_cal_set_time(2022, 6, 28, 18, 0, 14)
0>
0> <info> app:
0>
0> <debug> app: Uncalibrated time: 07/28/22 - 18:00:14

RE: nrf5-calendar-example SOFTDEVICE: INVALID MEMORY ACCESS

snowuyl — Tue, 28 Jun 2022 09:56:17 GMT

devzone.nordicsemi.com/.../53380.sdk_5F00_config.h

RE: nrf5-calendar-example SOFTDEVICE: INVALID MEMORY ACCESS

snowuyl — Tue, 28 Jun 2022 09:30:01 GMT

devzone.nordicsemi.com/.../4657.nrf_5F00_calendar.h devzone.nordicsemi.com/.../6888.nrf_5F00_calendar.c devzone.nordicsemi.com/.../nrf_5F00_calendar_5F00_time_5F00_incorrect.txt

RE: nrf5-calendar-example SOFTDEVICE: INVALID MEMORY ACCESS

snowuyl — Tue, 28 Jun 2022 09:28:56 GMT

No assert now. But time is not correct after calling nrf_cal_set_time(). The log message is as follows.

<debug> app: 2022-6-28 17:24:45
0>
0> <debug> app: nrf_cal_set_time(2022, 6, 28, 17, 24, 45
0>
0> <info> app:
0>
0> <debug> app: Uncalibrated time: 07/28/22 - 17:39:40
0>

RE: nrf5-calendar-example SOFTDEVICE: INVALID MEMORY ACCESS

Vidar Berg — Tue, 28 Jun 2022 09:22:53 GMT

Are you still getting the assert, or does it work now?

RE: nrf5-calendar-example SOFTDEVICE: INVALID MEMORY ACCESS

snowuyl — Tue, 28 Jun 2022 08:22:03 GMT

Thanks for your suggetion. I have changed nrf_calendar.h as follows.

// Change the following defines to change the RTC timer used or the interrupt priority
#define CAL_RTC                 NRF_RTC2
#define CAL_RTC_IRQn            RTC2_IRQn
#define CAL_RTC_IRQHandler      RTC2_IRQHandler
#define CAL_RTC_IRQ_Priority

RE: nrf5-calendar-example SOFTDEVICE: INVALID MEMORY ACCESS

Vidar Berg — Tue, 28 Jun 2022 08:03:18 GMT

Yes, RTC0 is reserved to the Softdevice as well, so you need to select another RTC instance.

In nrf_calendar.h, change:

// Change the following defines to change the RTC timer used or the interrupt priority
#define CAL_RTC                 NRF_RTC0
#define CAL_RTC_IRQn            RTC0_IRQn
#define CAL_RTC_IRQHandler      RTC0_IRQHandler
#define CAL_RTC_IRQ_Priority    3

To:

// Change the following defines to change the RTC timer used or the interrupt priority
#define CAL_RTC                 NRF_RTC2
#define CAL_RTC_IRQn            RTC2_IRQn
#define CAL_RTC_IRQHandler      RTC2_IRQHandler
#define CAL_RTC_IRQ_Priority    6

RE: nrf5-calendar-example SOFTDEVICE: INVALID MEMORY ACCESS

snowuyl — Tue, 28 Jun 2022 07:58:43 GMT

I have removed NRF_CLOCK related code from nrf_cal_init().Do you have any suggestion about how to change CAL_RTC related code to Softdevice APIs?

void nrf_cal_init(void) {
    NRF_LOG_DEBUG("nrf_cal_init() e\n");

    // Configure the RTC for 1 minute wakeup (default)
    CAL_RTC->PRESCALER = 0xFFF;
    CAL_RTC->EVTENSET = RTC_EVTENSET_COMPARE0_Msk;
    CAL_RTC->INTENSET = RTC_INTENSET_COMPARE0_Msk;
    CAL_RTC->CC[0] = m_rtc_increment * 8;
    CAL_RTC->TASKS_START = 1;

}

RE: nrf5-calendar-example SOFTDEVICE: INVALID MEMORY ACCESS

Vidar Berg — Tue, 28 Jun 2022 07:37:50 GMT

You don't need to start the LF clock either as the Softdevice does it when you enable it. So uou can remove this from cal_init():

    NRF_CLOCK->LFCLKSRC = CLOCK_LFCLKSRC_SRC_Xtal << CLOCK_LFCLKSRC_SRC_Pos;
    NRF_CLOCK->EVENTS_LFCLKSTARTED = 0;
    NRF_CLOCK->TASKS_LFCLKSTART = 1;
    while(NRF_CLOCK->EVENTS_LFCLKSTARTED == 0);

RE: nrf5-calendar-example SOFTDEVICE: INVALID MEMORY ACCESS

snowuyl — Tue, 28 Jun 2022 07:19:13 GMT

Do you have any suggestion about how to change NRF_CLOCK and CAL_RTC related code to Softdevice APIs?

RE: nrf5-calendar-example SOFTDEVICE: INVALID MEMORY ACCESS

snowuyl — Tue, 28 Jun 2022 07:16:33 GMT

Thanks for your reply! I have changed above code to the following code.

const ret_code_t errCode = sd_clock_hfclk_request();
    if (errCode != NRF_SUCCESS) {
        NRF_LOG_WARNING("sd_clock_hfclk_request() failed\n");
    }

    uint32_t hfclkIsRunning = 0;

    while (!hfclkIsRunning) {
        APP_ERROR_CHECK(sd_clock_hfclk_is_running(&hfclkIsRunning) );
    }

Now it hangs at nrf_cal_init() as the following error messages.

<debug> app: nrf_cal_init() e
0>
0> <error> app: SOFTDEVICE: INVALID MEMORY ACCESS

void nrf_cal_init(void) {
    NRF_LOG_DEBUG("nrf_cal_init() e\n");
    // Select the 32 kHz crystal and start the 32 kHz clock
    NRF_CLOCK->LFCLKSRC = CLOCK_LFCLKSRC_SRC_Xtal << CLOCK_LFCLKSRC_SRC_Pos;
    NRF_CLOCK->EVENTS_LFCLKSTARTED = 0;
    NRF_CLOCK->TASKS_LFCLKSTART = 1;
    while(NRF_CLOCK->EVENTS_LFCLKSTARTED == 0);
    NRF_LOG_DEBUG("1\n");

    // Configure the RTC for 1 minute wakeup (default)
    CAL_RTC->PRESCALER = 0xFFF;
    CAL_RTC->EVTENSET = RTC_EVTENSET_COMPARE0_Msk;
    CAL_RTC->INTENSET = RTC_INTENSET_COMPARE0_Msk;
    CAL_RTC->CC[0] = m_rtc_increment * 8;
    CAL_RTC->TASKS_START = 1;

}

RE: nrf5-calendar-example SOFTDEVICE: INVALID MEMORY ACCESS

Vidar Berg — Tue, 28 Jun 2022 06:46:07 GMT

Hello,

The app does not have write access to the CLOCK peripheral when the Softdevice is enabled, hence the assert (See Hardware peripherals). Instead you have to access it via the provided Softdevice APIs such as sd_clock_hfclk_request().

However, it should not be necessary to start HF crystal oscillator for the calendar library, so my suggestion would be to simply not include this code:

    NRF_CLOCK->EVENTS_HFCLKSTARTED = 0;
    NRF_CLOCK->TASKS_HFCLKSTART = 1;
    while(NRF_CLOCK->EVENTS_HFCLKSTARTED == 0);

Best regards,

Vidar

RE: nrf5-calendar-example SOFTDEVICE: INVALID MEMORY ACCESS

snowuyl — Tue, 28 Jun 2022 04:06:03 GMT

devzone.nordicsemi.com/.../1805.sdk_5F00_config.h

RE: nrf5-calendar-example SOFTDEVICE: INVALID MEMORY ACCESS

snowuyl — Tue, 28 Jun 2022 03:59:48 GMT

devzone.nordicsemi.com/.../nrf_5F00_calendar.h devzone.nordicsemi.com/.../nrf_5F00_calendar.c