This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Not in changelist - change to nrf_drv_timer.c in SDK 13.0.0

Not a question - but information for anyone similarly caught out.

In SDK 13.0.0 nrf_drv_timer_init() the p_config parameter must not be NULL. In SDK 12.2.0 and earlier NULL gave a default config.

Somehow my timer code, brought over from the earlier SDK, was still working - even with a NULL parameter - in SDK 13.0.0

Or rather it worked - until I added twis / i2c slave support - which casued the timer callback never to be called, but no other issues.

You can try this in the SDK timer example - change the 2nd parameter to NULL, and the exampel still runs.

Parents
  • FormerMember
    0 FormerMember

    There is a migratiion guide for migrating from SDK 12.2 to SDK 13.0.0 on the infocenter. Specifically, it has a section regarding the changes in the Timer library. The migration guide --> "Timer library" can be found here.

  • Thanks Kristin - generally the migration guidance is excellent, and you are correct regarding changes to the app timer.

    However the migration guide note appears to only be referencing changes to the app timer library - not changes to the drv timer component (hence it doesn't mention the particular case of nrf_drv_timer_init() no longer accepting a NULL second parameter).

    In the SDK, the "timer" example uses nrf_drv_timer, whilst the "simple timer" example uses the app timer.

Reply
  • Thanks Kristin - generally the migration guidance is excellent, and you are correct regarding changes to the app timer.

    However the migration guide note appears to only be referencing changes to the app timer library - not changes to the drv timer component (hence it doesn't mention the particular case of nrf_drv_timer_init() no longer accepting a NULL second parameter).

    In the SDK, the "timer" example uses nrf_drv_timer, whilst the "simple timer" example uses the app timer.

Children
No Data
Related