• State Not Answered
  • Replies 3 replies
  • Subscribers 25 subscribers
  • Views 282 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 281378
Options
nRF5 SDK is not maintained anymore
More Info: Consider nRF Connect SDK for new designs

Is it possible to update SDK without updating softdevice version?

user96737

Hi Team,

Currently in our project we use nrf52840 SDK15.2.0 and softdevice s140_nrf52_6.1.1_softdevice

Now we would like to update the SDK to 17.1.0 without updating the softdevice 

is this possible? can we update the SDK alone ?

Parents
  • 0

    Hi,

    Generally, SoftDevice with different major version numbers have API changes. And the SDK are only adapted to use the SoftDevices they ship with. That means that you will need to make some adjustments in the SDK code, and you will need to properly test this. There has not been a whole lot of changes during the last few SoftDevice released though, so you should not need a lot of effort to port SDK 17.1.0 to a 6.1.1 SoftDevice.

    I wonder why you want to keep the old SoftDevice though, can you elaborate on that? Why not just migrate to a updated SoftDevice as well?

  • 0 in reply to user7377

    Hi,

    Thanks for the info.

    since many of our users doesn't have the tool to update softdevice , we thought to update only sdk.

    i tried porting the SDK alone, after porting the examples are compiling fine but i see the below issue

    ble examples are working fine in Web Device CLI (makerdiary.com) and Serial Bluetooth Terminal

    but in nrf connect app data transmission is not happening as expected it stops after few bytes

    do you have any idea why this is happening?

Reply Children
  • 0 in reply to user96737

    I don't have any ideas from the top of my head, no. So you need to debug in order to see what is happening.

    Before that, please ensure that the basics is in place: You are using the header files for the SoftDevice you are actually using. Also, as there are API changes you will need to handle those. To see if you forgot some I recommend you read the SoftDevice migration document, which is quite detailed and describes all changes you need to take care of (in this case you would red it the other way, as you are migrating SDK 17.1.0 to an older SoftDevice, so start with the migration document for S140 7.2.0 and see all changes from 6.1.1, and ensure that you handle those. There are not many changes, though.

Related
Terms of service