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

Migrating old applications

superpak

Hi all,

I am developing for the nrf52xx boards. Let's say I want to migrate the example ble_app_uart from SDK v12.2 SoftDevice s132 3.0.0 to SDKv13.0 SoftDevice s132 v4.0.2.

How can I achieve this? I am actually trying to do this for a larger app, but I just want to use the example application ble_app_uart and understand how I can migrate it.

If I just copy the example from SDK v12.2 SoftDevice s132 3.0.0 to SDKv13.0 SoftDevice s132 v4.0.2, it gives me these errors saying "C:..\examples\bsp\bsp.c contains an incorrect path". It gives this error with other files in this project too.

Can someone guide me on how I can fix this? Thank you in advance for your help.

Parents
  • 0

    For SD part there is migration guide in every SD release. If you do too big jump you sometimes need to do i in several steps (= go through several SoftDevice migration documents). That should clear all SoftDevice API changes and help you to convert to new API whatever needed. For other SDK modules it's little bit more difficult: there are too many to cover it in any kind of detailed migration guide. So you need to do it as with any such software (source code) migration: put two SDK versions in KDiff and go through all modules you use change by change and evaluate the impact on your code. Yes, bloody work, that's why they still employ some SW engineers and not just machines...;)

Reply
  • 0

    For SD part there is migration guide in every SD release. If you do too big jump you sometimes need to do i in several steps (= go through several SoftDevice migration documents). That should clear all SoftDevice API changes and help you to convert to new API whatever needed. For other SDK modules it's little bit more difficult: there are too many to cover it in any kind of detailed migration guide. So you need to do it as with any such software (source code) migration: put two SDK versions in KDiff and go through all modules you use change by change and evaluate the impact on your code. Yes, bloody work, that's why they still employ some SW engineers and not just machines...;)

Children
No Data
Related
Terms of service