• State Not Answered
  • Replies 16 replies
  • Subscribers 65 subscribers
  • Views 3792 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 225698
Options
Beware that this post is related to an SDK in maintenance mode
More Info: Consider nRF Connect SDK for new designs
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

nRF5_SDK_12.3.0: updating s132 from v3.0.0 to 3.1.0.

Tom

I am further developing a solution based on nRF5_SDK_12.3.0 and s132 v3.1.0.

I am using Segger SES to Build and Run the solution in nRF52 SDK.

nRF5_SDK_12.3.0 comes with the older 3.0.0 version of s132.

I have downloaded and unzipped the v3.1.0 of s132, but I cannot find a way to put it into nRF5_SDK_12.3.0 or into the project folder so that it would be used by SES: the end result is always that either the older version 3.0.0 of s132 goes into the SDK or that the Build phase fails in SES because something is missing.

What should I do in order to set the system up so that the newer 3.1.0 version of s132 will be used when I use Build and Run in SES?

  • 0 in reply to Tom

    from the release note of S132v3.1, you can find the description of changes.  It implies that the header files with API have difference.  

    This is the minor change. Your application may have need to be modified which mention in the softdevice specification.

  • 0 in reply to Jimmy Wong

    Thanks. According to the original creator of the application it is already based on s132 v3.1.0, but it seems to work with v3.0.0. So I would expect that no modifications to the application are required.

  • 0 in reply to Bjørn Kvaale

    On the nRF5 SDK download page, if you select version 12.3.0 of the SDK, the proposed package includes also zip files for s130 v2.0.1 and s132 v3.1.0, but there are no instructions for how to replace the older versions built in to the SDK with these newer versions. These instructions are what I need now.

  • 0 in reply to Tom

    There are unfortunately no migration guides for minor softdevice releases (like from S132 v3.0.0 to S132 v3.1.0). I agree with Jimmy that the main "migration guide" is to do what Jimmy did. There should not be many changes needed to make the new softdevice work with your application. Make sure that the header files are included correctly in the "user include directories" in SES. There may be some header function API changes from S132 v3.0.0 to S132 v3.1.0 like Jimmy mentioned, but this will most likely only be minor changes.

    Do you get an error codes or any missing header files when you implement what Jimmy mentions? If your colleague says it worked with S132 v3.1.0, maybe it will work out of the box?

  • 0 in reply to Bjørn Kvaale

    Thanks. I will try by copying the files from the downloaded 3.1.0 version of s132 to the s132 folder in the SDK. For some reason their folder and file structures are very different so it is not clear what and where to copy. Last time I tried my best but SES could not find a certain header file - but I did not write down the name of that file and I cannot remember it either.

Related