• State Verified Answer
  • Locked Locked
  • Replies 1 reply
  • Subscribers 74 subscribers
  • Views 3621 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 280176
Options
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

what is the difference between nRF5 SDK and nRF connect SDK?

Yadhu KP

Hi,

We are using nRF52832 and nRF5 SDK(SDK 15 - ble_app_hid_mouse example) for our application, it is already a completed product and we are working on its modifications and support. Now I come across on nRF connect SDK so I have the following questions regarding it.

  1. what exactly is the difference between these two?
  2. is there any advantage for nRF connect SDK over nRF5 SDK?
  3. do we need to migrate from nRF5 SDK to connect SDK?
  4. are there any guidelines on migration?
  5. what is the best method to start on nRF connect SDK?

thanks in advance 

Yadhu KP

Parents
  • +1

    Hi Yadhu,
    (My response is just my personal opinion and knowledge I have)

    1. The biggest difference is, that nRF Connect SDK uses Zephyr OS, which is RTOS, and nRF5 SDK is mostly bare-metal. Zephyr OS is not targeting only Nordic SoCs, but also from other manufacturers.
    2. Firstly, nRF Connect SDK supports nRF5340 series, where nRF5 SDK doesn't, also it provides more consistent development between SoCs, and you don't need separate SDK for Mesh or AppleKit  features.
    3. At the moment, no, nRF5 SDK is planned to be maintained, but by my personal opinion, the new features will be not added much there, as most of focus is aimed on nRF Connect SDK
    4. I don't know, most likely, although, the controlling Bluetooth is different, using peripherals is different, so I think it will require a lot of refactoring
    5. I think there should be Mouse HID example also in Zephyr, so you can try it out as first thing. There are pretty good series about how to start with nRF COnnect SDK on Youtube
Reply
  • +1

    Hi Yadhu,
    (My response is just my personal opinion and knowledge I have)

    1. The biggest difference is, that nRF Connect SDK uses Zephyr OS, which is RTOS, and nRF5 SDK is mostly bare-metal. Zephyr OS is not targeting only Nordic SoCs, but also from other manufacturers.
    2. Firstly, nRF Connect SDK supports nRF5340 series, where nRF5 SDK doesn't, also it provides more consistent development between SoCs, and you don't need separate SDK for Mesh or AppleKit  features.
    3. At the moment, no, nRF5 SDK is planned to be maintained, but by my personal opinion, the new features will be not added much there, as most of focus is aimed on nRF Connect SDK
    4. I don't know, most likely, although, the controlling Bluetooth is different, using peripherals is different, so I think it will require a lot of refactoring
    5. I think there should be Mouse HID example also in Zephyr, so you can try it out as first thing. There are pretty good series about how to start with nRF COnnect SDK on Youtube
Children
No Data
Related
Terms of service