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?

[Jimmy Wong]

I did the example on the NRF51 with SDK 12.3 SES project.  It should be very similar to nRF52 if you use it as reference.

[Jimmy Wong]

https://github.com/jimmywong2003/SES_Project_for_nRF51

[Jimmy Wong]

Hi, 

the folder of the softdevice is placed at SDK12.3/components/softdevice/S132.

[Tom]

Yes, I know. I think that I already once replaced the contents with the downloaded and unzipped contents of the new s132, but then the Build in SES reported errors and did not go through - it reported that it could not find a certain file in the SDK. But I can retry this if this is what you did.

[Bjørn Kvaale]

Which file is missing? What is the error you are receiving?

[Tom]

At the moment I am using the s132 v3.0.0 that is built into SDK 12.3.0, so it is not so easy to check again. But I remember that SES reported in the Build phase that it could not find a .h file that was supposed to be inside the SDK. If you could propose what to do in order to update the s132 to v3.1.0, I will do it and report back what the result is. I already have the new s132 version downloaded and unzipped, I just need a proposal what to do with it.

[Jimmy Wong]

You can do the following steps.

Step 1:

Copy the header files from 132_nrf52_3.1.0\s132_nrf52_3.1.0_API\include and rename them inside the folder

nRF5_SDK_12.3.0_d7731ad\components\softdevice\s132\header

Step 2:

check the path "c_user_include_directories" inside file (ble_app_uart_pca10040_s132.emProject) (after you port the my example from nRF51 to nRF52) to use the correct softdevice path.

[Tom]

It seems that Build and Run in SES flashes the hex file of s132 into the nRF52 DK, so I assume that copying only the header files from the newer version will solve the problem.

[Jimmy Wong]

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.

[Tom]

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.