• State Verified Answer
  • Replies 11 replies
  • Answers 1 answer
  • Subscribers 89 subscribers
  • Views 2606 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 272499
Options
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

How is NCS better than SDK17?

myself

Hi sir,

  I would like to know the advantages of NCS to illustrate customer adoption NCS.

  Thank you and best regards.

Parents
  • +1

    nRF5_SDK is freedom

    with NCS you're a slave. You do as you're told.

  • +1 in reply to Nguyen Hoan Hoang

    Let me clarify, the idea that SDK is deprecated has been suggested in Webinars about NCS, so it comes from Nordic. Of course, SDK will continue to receive corrections, but not any new features, that is my understanding. For an existing product, there may be no reason to switch.

    For a new product beyond BLE connectivity (IP connectivity, Thread, Zigbee, CHIP ...) I would really recommend to switch.

    Here is why I switch to NCS for teaching, and this experience might convince you: My aim was to build a toy light control system with LWM2M connectivity for my students. SDK as NCS integrate OpenThread, but that is really where things get messy as one would have to port a LWM2M client to work with the openthread IP API. It's possible, but why do it when you get this combination in NCS for free?!

    In NCS/Zephyr, there is a much better chance to have third party software components integrated and it is in fact easy to get the LWM2M demos running on Nrf52833 and Nrf52840 with OpenThread and the Zephyr IP stack. No line of code had to be adapted, only you have to configure the compilation to make it work. And that is the great thing about NCS, there are not only good APIs for IP, with KConfig you can plug different implementations of different platforms together and it works. True modular software!

    I agree though that NCS/Zephyr has a steep learning curve and that you have to understand concepts that just would not occur with SDK, notably KConfig and DeviceTree. On the other hand, for an embedded software engineer who might touch embedded Linux as well, learning at least about DeviceTree is a very useful thing to do. That does take time so be prepared for it.

  • 0 in reply to niebert

    I think you are not right about nRF5 SDK being deprecated, please point at your sources. NCS is just not ready for production use on the nRF52 series.

Reply Children
No Data
Related
Terms of service