Hi there,
I'm struggling to find straight forward peripheral interface documentation for an NCS project. I see there's something called nrfx (https://github.com/NordicSemiconductor/nrfx) and also Zephyr has peripheral APIs (https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/zephyr/reference/peripherals/index.html). Which is correct?
For nrfx, I don't see any examples of usage of this. For Zephyr APIs, how do I configure them?
Thanks
If you would like to fully utilize all the advantages Zephyr brings with it, I would recommend you to use the Zephyr API. In Zephyr you use Kconfigs (through prj.conf) and the device tree/dts (through overlay files) to set up a project, read more about this in 1. Concepts in NCS. If you use the nrfx layer, the stuff you've set in prj.conf and overlay files (and all the other Kconfig and dts files) will not be seen. Using the Zephyr API makes it quicker and easier to set up a project (Given that everything works as expected and you have a good intuitive understanding of how the SDK works). There might be more advantages of using the Zephyr API that I have missed, but this is what I though of right now.
Some developers likes to have more control over what they're doing, with less abstractions from the hardware, then the nrfx drivers might be a better option.
From my point of view, I would recommend you to use the Zephyr API, as it will reduce the development time, make the application more scalable/portable/cross-compatible and reduce the amount of code you write (less chances of bugs). I don't have a complete overview of this, so if anyone could prove me wrong on any of these points, I would be more than happy.
Since NCS/Zephyr is still quite new, there are circumstances where the nrfx layer has to be used. E.g. if you want to use I2S with Zephyr, you have to use the nrfx drivers, since it's not supported on the top layer (I think there is on-going work right on this right now).
Shaney is correct in that the Zephyr API uses the nrfx drivers. The figure below (from NCS tutorial part 3) might give you an overview of how it works:
Best regards,
Simon
If you would like to fully utilize all the advantages Zephyr brings with it, I would recommend you to use the Zephyr API. In Zephyr you use Kconfigs (through prj.conf) and the device tree/dts (through overlay files) to set up a project, read more about this in 1. Concepts in NCS. If you use the nrfx layer, the stuff you've set in prj.conf and overlay files (and all the other Kconfig and dts files) will not be seen. Using the Zephyr API makes it quicker and easier to set up a project (Given that everything works as expected and you have a good intuitive understanding of how the SDK works). There might be more advantages of using the Zephyr API that I have missed, but this is what I though of right now.
Some developers likes to have more control over what they're doing, with less abstractions from the hardware, then the nrfx drivers might be a better option.
From my point of view, I would recommend you to use the Zephyr API, as it will reduce the development time, make the application more scalable/portable/cross-compatible and reduce the amount of code you write (less chances of bugs). I don't have a complete overview of this, so if anyone could prove me wrong on any of these points, I would be more than happy.
Since NCS/Zephyr is still quite new, there are circumstances where the nrfx layer has to be used. E.g. if you want to use I2S with Zephyr, you have to use the nrfx drivers, since it's not supported on the top layer (I think there is on-going work right on this right now).
Shaney is correct in that the Zephyr API uses the nrfx drivers. The figure below (from NCS tutorial part 3) might give you an overview of how it works:
Best regards,
Simon
