• State Verified Answer
  • Replies 2 replies
  • Subscribers 75 subscribers
  • Views 603 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 319219
Options

nRF Connect SDK - Latest dev has GPIOTE driver changed from latest stable release - Related example in zephyr not provided yet

Marco Russi

Hello,

I need to use GPIOTE and DPPi peripheral for a project and I have a dilemma. I have noticed that latest stable SDK release (2.5.0) has GPIOTE APIs different than the latest development. So I guess you have been modifying the GPIOTE and it will be done and tested in the next stable release. I saw the changes from the documentation portal https://docs.nordicsemi.com/bundle/ncs-2.5.99-dev1/page/nrfx/drivers/gpiote/driver.html

Indeed latest update of the GPIOTE driver is today. 

I have checked out latest dev of the SDK repo and updated all module via west update. Unfortunately it looks like that the related zephyr example in samples/boards/nrf/nrfx still used the previous APIs. 

Am I correct?

Anyway, what would you recommend to do? Use the new APIs or stick with the stable version? I wonder that if I do not use the new APIs then I'll have to change the code in the future. It is not recommended to start a new project with some already obsolete code.

The chipset is the nRF5340. 

Thank you for your help.

Parents
  • +1

    Hi Marco

    I strongly recommend using the latest stable NCS release (v2.5.0) instead of the development tag, which is under constant development and has changes made to it almost daily. I would only recommend using the dev-tag if you are dependent of any of the features in it and are using that while waiting for the next official release. If you are happy with the GPIOTE API in NCS 2.5.0 I recommend you stick to NCS 2.5.0.

    It should not be necessary to change the project in the future unless you need to upgrade the entire project to support some feature(s) not available in NCS 2.5.0, and even then it's likely possible to just cherry-pick whatever you need from later releases and add to your project.

    Best regards,

    Simon

Reply
  • +1

    Hi Marco

    I strongly recommend using the latest stable NCS release (v2.5.0) instead of the development tag, which is under constant development and has changes made to it almost daily. I would only recommend using the dev-tag if you are dependent of any of the features in it and are using that while waiting for the next official release. If you are happy with the GPIOTE API in NCS 2.5.0 I recommend you stick to NCS 2.5.0.

    It should not be necessary to change the project in the future unless you need to upgrade the entire project to support some feature(s) not available in NCS 2.5.0, and even then it's likely possible to just cherry-pick whatever you need from later releases and add to your project.

    Best regards,

    Simon

Children
Related
Terms of service