• State Verified Answer
  • Locked Locked
  • Replies 1 reply
  • Subscribers 24 subscribers
  • Views 79 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 289431
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

Is there any material that describes how to update SoftDevice?

user104365

Hello.

We are developing using nrf52832 (s132 v7.0.1, SDK v17.0.0) as a peripheral device.

I would like to update SoftDevice from v7.0.1 to v7.3.0.
Are there any areas that need to be changed or should be noted when updating?
Also, are there any materials that describe how to update? I looked for it but couldn't find it.

Best regards.

Parents
  • +1

    Hello,

    You can look in the migration-documents for the softdeivce, which is located in:

    SDK\components\softdevice\s1XX\doc\sXX_nrf52_7.X.X_migration-document.

    For the standalone softdevices that didn't come with an SDK, you will find the same document in the doc\ folder. If you open the migration guide from the latest softdevice, it will contain the migration guide for the previous releases as well. 

    That being said, migrating between minor updates (7.x.x -> 7.y.y) is quite straight forward. There shouldn't be any API changes, and the footprint should be the same, so I think you can just replace the old hex file and header files in SDK\components\softdevice\s132\headers with the new one.

    Best regards,

    Edvin

Reply
  • +1

    Hello,

    You can look in the migration-documents for the softdeivce, which is located in:

    SDK\components\softdevice\s1XX\doc\sXX_nrf52_7.X.X_migration-document.

    For the standalone softdevices that didn't come with an SDK, you will find the same document in the doc\ folder. If you open the migration guide from the latest softdevice, it will contain the migration guide for the previous releases as well. 

    That being said, migrating between minor updates (7.x.x -> 7.y.y) is quite straight forward. There shouldn't be any API changes, and the footprint should be the same, so I think you can just replace the old hex file and header files in SDK\components\softdevice\s132\headers with the new one.

    Best regards,

    Edvin

Children
No Data
Related
Terms of service