Why are legacy files driving SDK 16 examples?

[Cy]

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?

[Simonr]

Hi

Most of the old legacy files were split into an nrfx and a legacy layer in order to make it easier to integrate the low-level part (nrfx) in other software platforms. In some cases, using nrfx directly is not a good idea due to this, and therefore we generally advise developers to use the nrf_drv_* files/functions instead of the nrfx_* versions. The term "legacy" gives the wrong idea really. It's better to think of it like this: nrfx is a platform-independent low-level driver package, while the legacy files are an integration layer for integrating it into the nRF5 SDK.

So, there are no plans as of now to remove either layer, as they fulfill different tasks really, and the "legacy" layer is not outdated, but rather simpler.

Best regards,

Simon

[Cy]

Simon,

Thank you, but could you give me an example of the ease of integration of which you speak in regards to the low-level part?