• State Verified Answer
  • Replies 5 replies
  • Subscribers 89 subscribers
  • Views 870 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 270882
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Which Dev platform

fgeldenh

I have been developing products for nRF52832 and nRF52840 for some years now. I am aware that you have released the NRF Connect SDK. To date I have only used the nRF5 SDK. although I did get a small application going with NRF Connect. It seems to me that compared to nRF5 SDK NRF Connect SDK is lacking in documentation and functionality. Take for instance a simple issue like changing the advertisement name on the fly. I spent hours trying to find out how to do this in NRF Connect to no avail.

I am missing something?

Can I continue with NRF5 SDK and know that it will be future proof?

Thank You

Francois Geldenhuys

Parents
  • 0

    Hi Francois,

    We will still continue to support nRF5 SDK, and as said, there will still be bug fixes and security updates. If you are already developing or have developed an application using nRF5 SDK there is no problem continuing with that SDK, but be aware that it will not receive any updates besides what is mentioned. So there will be no new features or functionality added. If this is not important to you, you can continue with nRF5 SDK if you prefer that, but if you want to be able to use new features that are not in the SDK already, I would recommend switching to NCS.

    As for changing the advertisement name in NCS, you can use the function bt_set_name() to set the device name, and then bt_le_adv_update_data() to update advertising. You can see an example of this being used in the ble_handler module in the Connectivity Bridge application here.

    Best regards,

    Marte

Reply
  • 0

    Hi Francois,

    We will still continue to support nRF5 SDK, and as said, there will still be bug fixes and security updates. If you are already developing or have developed an application using nRF5 SDK there is no problem continuing with that SDK, but be aware that it will not receive any updates besides what is mentioned. So there will be no new features or functionality added. If this is not important to you, you can continue with nRF5 SDK if you prefer that, but if you want to be able to use new features that are not in the SDK already, I would recommend switching to NCS.

    As for changing the advertisement name in NCS, you can use the function bt_set_name() to set the device name, and then bt_le_adv_update_data() to update advertising. You can see an example of this being used in the ble_handler module in the Connectivity Bridge application here.

    Best regards,

    Marte

Children
Related
Terms of service