Beware that this post is related to an SDK in maintenance mode
More Info: Consider nRF Connect SDK for new designs
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Why are legacy files driving SDK 16 examples?

I could use some clarity on the legacy drivers/files, nrf,driving example applications inside SDK 16. Is it just too much work to clean up the examples with current drivers? Are all the legacy files just hooked into the current drivers/files, nrfx, thorugh many many many defines to keep current. I am just fuzy on the structure of the nrf and nrfx drivers, when to use what?

Parents
  • You can check out our nrfx driver migration guide to see how you can migrate any project to start using only the nrfx drivers and their benefits. You should also check out the nrfx_config.h file located in <sdkdir>/modules/nrfx/templates/<board> which is a clean nrfx configuration header to use in nrfx projects. It is the nrfx drivers that are being used as a baseline in the SDK, and the legacy layer is used to translate the old API to the new one. The legacy layer is used for backward compatibility.

    Best regards,

    Simon

Reply
  • You can check out our nrfx driver migration guide to see how you can migrate any project to start using only the nrfx drivers and their benefits. You should also check out the nrfx_config.h file located in <sdkdir>/modules/nrfx/templates/<board> which is a clean nrfx configuration header to use in nrfx projects. It is the nrfx drivers that are being used as a baseline in the SDK, and the legacy layer is used to translate the old API to the new one. The legacy layer is used for backward compatibility.

    Best regards,

    Simon

Children
Related