Problem running LESC on nRF5 SDK with App Scheduler running

RE: Problem running LESC on nRF5 SDK with App Scheduler running

Vidar Berg — Mon, 15 Jul 2024 06:57:36 GMT

Hi Sunny.

Good to hear. If you want, I can take a look at your FDS code to see if I can spot any potential problems with the implementation. Just let me know.

RE: Problem running LESC on nRF5 SDK with App Scheduler running

Sunny Lo — Mon, 15 Jul 2024 02:20:10 GMT

Hi Vidar,

Oh yes. The demo is running ok now. Thanks.

I still see problems with my code in the section running the fds storage. I will spend time looking at it.

Best regards

Sunny

RE: Problem running LESC on nRF5 SDK with App Scheduler running

Vidar Berg — Fri, 12 Jul 2024 08:58:20 GMT

Hi,

APP_ERROR_HANDLER() calls the error handler function regardless of what the error code is. You probably meant to use APP_ERROR_CHECK().

RE: Problem running LESC on nRF5 SDK with App Scheduler running

Sunny Lo — Fri, 12 Jul 2024 08:37:00 GMT

Hi Vidar,

Yes, you are right. I missed the APP_SCHED_INIT macro. Now I added it back. The timer use scheduler works. But something strange happens if I add the app_sched_execute() in the idle_state_handle().

As long as I add the macro APP_ERROR_HANDLER(err_code) after the app_sched_event_put(...), an error pops up. If I remove this macro, everything works fine. Do you see anything wrong with my code?

Commented out APP_ERROR_HANDLER(err_code), no error. Program runs fine.

With APP_ERROR_HANDLER(err_code), program halt even though the error code is "ERROR 0 [NRF_SUCCESS]"

RE: Problem running LESC on nRF5 SDK with App Scheduler running

Vidar Berg — Thu, 11 Jul 2024 10:16:24 GMT

Hi Sunny,

It seems like you may have forgotten to initialize the scheduler with APP_SCHED_INIT(SCHED_MAX_EVENT_DATA_SIZE, SCHED_QUEUE_SIZE); in main()?

Best regards,

Vidar

RE: Problem running LESC on nRF5 SDK with App Scheduler running

Sunny Lo — Thu, 11 Jul 2024 08:49:46 GMT

Hi Vidar,

Thank you for your reply.

You are right that the modified code from glucose example was not a hard fault. Instead it is ERROR 4 [NRF_ERROR_NO_MEM]. Sorry about that.

However, I don't understand why this error happens. What I have changed to the glucose example was to add a 1 second counter from the app timer. When it reaches 30 times (roughly 30 seconds), it puts the event check_if_put_bmr_to_sleep_seh into the scheduler queue. In fact, it only happens once and the NRF_ERROR_NO_MEM error shows up. I don't understand why putting 1 single event into the scheduler event queue cause this NRF_ERROR_NO_MEM error. I have probably overlook something. Can you please educate me on it?

/* 
   Added timestamp to the log
*/
static uint64_t   m_clock_cnt;

uint32_t get_rtc_counter(void)
{
    return NRF_RTC1->COUNTER;
}

/**@brief Function for initializing the nrf log module.
 */
static void log_init(void)
{
    ret_code_t err_code = NRF_LOG_INIT(get_rtc_counter);
    APP_ERROR_CHECK(err_code);

    NRF_LOG_DEFAULT_BACKENDS_INIT();
}
......

static void timers_init(void)
{
    ret_code_t err_code;

    // Initialize timer module.
    err_code = app_timer_init();
    APP_ERROR_CHECK(err_code);

    // Create timers.
    err_code = app_timer_create(&m_battery_timer_id,
                                APP_TIMER_MODE_REPEATED,
                                battery_level_meas_timeout_handler);
    APP_ERROR_CHECK(err_code);

    // Timer to emulate clock
    err_code = app_timer_create(&clock_em_tid, APP_TIMER_MODE_REPEATED, clock_em_eh);   
    APP_ERROR_CHECK(err_code);                                                                        

}


static void application_timers_start(void)
{
    ret_code_t err_code;

    // Start application timers.
    err_code = app_timer_start(m_battery_timer_id, BATTERY_LEVEL_MEAS_INTERVAL, NULL);
    APP_ERROR_CHECK(err_code);

    // Start clock emulation timer
    err_code = app_timer_start(clock_em_tid, APP_TIMER_TICKS(1000), NULL);
    m_clock_cnt = 0; 
    APP_ERROR_CHECK(err_code);
}

void check_if_put_bmr_to_sleep_seh(void *p_ev_data, uint16_t ev_size) {
    NRF_LOG_INFO("Reached 30 seconds! Reset clock counter to ZERO!");
}

/**@brief Function to check if bmr should be put to sleep
 *
 * @details if m_clock_cnt >= 30; reset m_clock_cnt = 0; 
*/
void check_if_put_bmr_to_sleep() {
    ret_code_t  err_code;
    if (m_clock_cnt >= 30) {
        m_clock_cnt = 0;

        NRF_LOG_INFO("Put function in Scheduler!");
        err_code = app_sched_event_put(0,0,check_if_put_bmr_to_sleep_seh);
        APP_ERROR_CHECK(err_code);
    }
}

/**@brief Function for the 1 second clock emulation.
 *
 * @details Run every 1 second
 */
void clock_em_eh(void *p_context) {
    UNUSED_PARAMETER(p_context);
    m_clock_cnt++;
    check_if_put_bmr_to_sleep();

}

BTW, I use the original Glucose Application main.c without making any changes. Then I change the following

#define APP_TIMER_CONFIG_USE_SCHEDULER 1

#define NRF_LOG_BACKEND_RTT_ENABLED 1

#define NRF_LOG_BACKEND_UART_ENABLED 0

in sdk_config.h

Then the error ERROR 9 [NRF_ERROR_INVALID_LENGTH] shows up. I think I must be missing something here. Please help.

Thank you.

Best Regards

Sunny

RE: Problem running LESC on nRF5 SDK with App Scheduler running

Vidar Berg — Thu, 11 Jul 2024 07:21:34 GMT

Hello,

The issues you are seeing does not appear to be related to LESC. I'm not aware of any known issues with using LESC and the app scheduler together either.

[quote user=""]3. After I started debugging in SES, I got the DH_key and had completed the connection. However, once the "app_sched_event_put(0,0,check_if_put_bmr_to_sleep_seh)" was executed the hardfault error (timer_expire) came out. [/quote]

The first screenshot you posted was showing a hardfault, but this one is not. The error handler is invoked because a runtime error check failed in the timer_expire() function. Perhaps you have exhausted the scheduler queue due to long-running tasks. If that's the case, it's likely failing here:

You will get a more detailed crash log if you debug your project using the 'Debug' build configuration instead of 'Release'

Best regards,

Vidar