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

Development for nRF52832: nRF5 SDK +SES or NRF Connect SDK and nRF Connect for Desktop?

I am starting the development of a product using the nRF52 DK for the nRF52832 SoC.

The product will use some peripherals (RTC, NVMC, Timers) and communicate using BLE and NFC with a smartphone. It will also feature Firmware updates over BLE. There is no need (at least for this stage of the product), to use any RTOS.

So far, I am unable to understand if the recommend development toolchain is to use Segger Embeded Studio with the NRF5 SDK, as detailed here, or if I should start to use already the nRF Connect SDK with the nRF Connect for Desktop, which features a SEGGER Embedded Studio Nordic Edition.

I am aware of this thread, but I believe my question is broader. What is the recommended toolchain (IDE and other tools) and SDK to use in new nRF52832 products?

Thank you in advance

Parents Reply
  • Thank you for the clarifications

    Further reading brought me another doubt. The recommend SDK is the NRF5, but here it is stated that "The nRF Connect platform now adds support for Nordic’s popular nRF52 Series SoCs". 

    Not to invalidate the previously discussed points and outcomes, but since the project is starting, I have two further questions:

    1. How does NRF Connect SDK support for the NRF52 Series SoCs compare to the NRF5 SDK? My main concerns are the number of features and performance.

    2. Which SDK is more "future-proof" for development windows of 2/3 years? I.e., will NRF5 SDK lose support and development time in favour of the NRF Connect SDK? 

    I really appreciate if you could clarify on those topics.

Children
Related