[NRF SDK 17] Trooble with app_timer when migrate from sdk 16 to 17

RE: [NRF SDK 17] Trooble with app_timer when migrate from sdk 16 to 17

Jørgen Holmefjord — Tue, 03 Aug 2021 14:23:05 GMT

I see that you have mixed configs in the posted snippet (NRFX configs and legacy nrf_drv configs). If you have the legacy configs defined (regardless of whether they are set to 1 or 0), the NRFX configs will be overwritten in apply_old_config.h.

Can you post the full project for us to reproduce and debug this issue?

RE: [NRF SDK 17] Trooble with app_timer when migrate from sdk 16 to 17

neicureuil — Mon, 02 Aug 2021 10:02:21 GMT

Hi,

I have remove the ampersand reference but the same issue appear.

When I don't use WDT, all works fine but when I use it (only init it, not feed it => to try if its works if its never feed) my timer never create an interrupt and the WDT never reboot the board or call the event function.

All of my interrupt (WDT, timer and uart) have their irq priority set to 6.

Some of my WDT config in my sdk config :

// <1=> Run in SLEEP, Pause in HALT
// <8=> Pause in SLEEP, Run in HALT
// <9=> Run in SLEEP and HALT
// <0=> Pause in SLEEP and HALT
#ifndef NRFX_WDT_CONFIG_BEHAVIOUR
#define NRFX_WDT_CONFIG_BEHAVIOUR 1
#endif


// <1=> Run in SLEEP, Pause in HALT
// <8=> Pause in SLEEP, Run in HALT
// <9=> Run in SLEEP and HALT
// <0=> Pause in SLEEP and HALT
#ifndef WDT_CONFIG_BEHAVIOUR
#define WDT_CONFIG_BEHAVIOUR 1
#endif


// <0=> Include WDT IRQ handling
// <1=> Remove WDT IRQ handling
#ifndef NRFX_WDT_CONFIG_NO_IRQ
#define NRFX_WDT_CONFIG_NO_IRQ 0
#endif

Regards

RE: [NRF SDK 17] Trooble with app_timer when migrate from sdk 16 to 17

Jørgen Holmefjord — Mon, 02 Aug 2021 09:27:11 GMT

Hi,

Please try to remove the ampersand reference from the event handler in the init function:

uint32_t err = nrfx_wdt_init(&wdt_config, watdog_evt_handler);

Also, make sure that NRFX_WDT_CONFIG_NO_IRQ is not set in your sdk_config.h file.

Have you verified that the error codes returned from nrfx_wdt_init() and nrfx_wdt_channel_alloc() is NRF_SUCCESS/zero?

Best regards,
Jørgen

RE: [NRF SDK 17] Trooble with app_timer when migrate from sdk 16 to 17

neicureuil — Mon, 02 Aug 2021 08:29:39 GMT

Hi, I have tried to update my watchdog code but it didn't work anymore.

My watchdog init without error but never be trigger even if i never feed it. (I never enter in the event handler function and the board never reboot)

#include "watchdog.h"

#include "nrfx_wdt.h"
#include "boards.h"
#include "nrf_log.h"

// The watchdog timeout in seconds
#define WATCHDOG_TIMEOUT_S 30
// The watchdog channel
static nrfx_wdt_channel_id* wtd_channel;

// Watchdog event handler
void watdog_evt_handler(void)
{
  NRF_LOG_INFO("WDT Evt");
}

// Initialize the watch dog
void watchdog_init(void)
{
  nrfx_wdt_config_t wdt_config = NRFX_WDT_DEAFULT_CONFIG;
  uint32_t err = nrfx_wdt_init(&wdt_config, &watdog_evt_handler);  
  uint32_t err2 =nrfx_wdt_channel_alloc(wtd_channel);
  nrfx_wdt_enable();
  NRF_LOG_INFO("Watchdog init %x - %x", err, err2);
}

// Feed the watchdog
void watchdog_feed(void)
{
  nrfx_wdt_channel_feed(*wtd_channel);
}

Regards

RE: [NRF SDK 17] Trooble with app_timer when migrate from sdk 16 to 17

neicureuil — Mon, 02 Aug 2021 07:30:14 GMT

Hi,

I just saw that I'm not using the app_timer but the app_timer_mesh.c because I'm based on the sdk coexist example.

The problem disappear when I remove the watch dog so I think its this that cause the issue.

Is my watchdog specific code correct for sdk 17 and mesh sdk 5.0 ?

Regards

RE: [NRF SDK 17] Trooble with app_timer when migrate from sdk 16 to 17

Jørgen Holmefjord — Thu, 29 Jul 2021 12:46:15 GMT

The source file of app_timer_v2 uses a different name, app_timer2.c, while the old app_timer is named app_timer.c. You will also have additional preprocessor symbols defined for APP_TIMER_V2 in the project.

It would be helpful if you can debug the application to see if it gets stuck somewhere. That is the only reason I can think of that should cause this problem.

RE: [NRF SDK 17] Trooble with app_timer when migrate from sdk 16 to 17

neicureuil — Wed, 28 Jul 2021 07:25:04 GMT

Hi,

How can I now which app_timer version I used ?

Also, after few tests, Its seems to be the Watchdog that cause this issue but I don't understand why.

Regards

RE: [NRF SDK 17] Trooble with app_timer when migrate from sdk 16 to 17

Jørgen Holmefjord — Tue, 27 Jul 2021 14:34:49 GMT

Hi,

Have you debugged the application to see if it gets stuck somewhere?

What is the clock configuration for the LFCLK?

Are you using app_timer_v2, or the old app_timer?

Can you post the full project, for us to reproduce and debug this issue?

Best regards,
Jørgen