thanks much. Yes we need to use zephyr as we are accessing some lower level radio information that is not available in the SDK. We are on the 833 moving to the 840 when the devkit is production.
You mean information from the Bluetooth stack? Otherwise I am not sure Zephyr will give you more access.
Either way there is no official recommendation from Nordic on what displays or ethernet ports to use. As long as the nRF52 device supports the same interfaces, voltage levels etc you should be able to use whichever ones you prefer. When it comes to displays in particular there are so many different types available, and every application will have different requirements in terms of size, resolution, display type and so forth.
Since the case is public there might be some input from the community, if someone else has tried the same.
We have already go what we need from the radio, so Zephyr does the job we need it to do. Are there recommendations on the ethernet or wifi for use with the SDK? I could start with those if that is the case.
We have already go what we need from the radio, so Zephyr does the job we need it to do. Are there recommendations on the ethernet or wifi for use with the SDK? I could start with those if that is the case.
It shows an example of an Ethernet module connected to the nRF52, and there is a link to the software repository in the blog.
Please be aware that this project hasn't been updated in 3 years and use a very old SDK version. If you do decide to go down this route I would recommend trying to port the driver to a later SDK.
Also, this is not a Nordic delivery, and as such is not officially supported by us.
