• State Verified Answer
  • +1 person also asked this people also asked this
  • Replies 8 replies
  • Subscribers 68 subscribers
  • Views 2701 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 243421
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Soft device 132 to S112 migration for nRF SDK Blinky example

AliMahmood123

Hello

I am facing extreme difficulty migrating soft devices for nRF SDK16, nRF 52832 - S132 to S112 on the nRF DK pca10040 package

I have consulted the following example for this procedure:

https://devzone.nordicsemi.com/f/nordic-q-a/40925/replace-s132-with-s112/159683#159683

And the simple global replacing with memory specification changes doesn't seem to work. It gives me a few errors. There is lack of migration support from Nordic which is very frustrating

We are just in the initial development phase and would like to use blinky example as our benchmark. I can't make the blinky example work with S112 despite following the steps mentioned in the link.

Please convert the ble_app_blinky example to S112 and guide me the steps here.

Thanks in advance

Ali

Parents
  • +1

    Hi Muhammad

    I've edited the ble_app_blinky project in SDK v.16.0.0 to use S112 instead of S132. Here are the necessary steps:

    1. Create a new folder in \nRF5_SDK_16.0.0_98a08e2\examples\ble_peripheral\ble_app_blinky\pca10040\ called s112 to make sure you still have the original project.
    2. Copy all files from \nRF5_SDK_16.0.0_98a08e2\examples\ble_peripheral\ble_app_blinky\pca10040\s132\ into this new folder.
    3. Open the .emproject file with Segger Embedded Studios.
    4. Open the project options in SES and set the build configuration to Common.
    5. Go to Linker, open Section Placement Macros, and change FLASH_SIZE, FLASH_START, RAM_START, and RAM_SIZE to the appropriate values for S112.
    6. Go to Preprocessor, open Preprocessor Definitions and change S132 to S112. 
    7. Open User Include Directories and change ../../../../../../components/softdevice/s132/headers &../../../../../../components/softdevice/s132/headers/nrf52 to ../../../../../../components/softdevice/s112/headers & ../../../../../../components/softdevice/s12/headers/nrf52
    8. Go to Loader (under Debug), open Additional Load File[0] and change this to /YOUR_SDK_FOLDER/nRF5_SDK_16.0.0_98a08e2/components/softdevice/s112/hex/s112_nrf52_7.0.1_softdevice.hex
    9. Compile, build, and run your project, and that should be it.

    Best regards,

    Simon

Reply
  • +1

    Hi Muhammad

    I've edited the ble_app_blinky project in SDK v.16.0.0 to use S112 instead of S132. Here are the necessary steps:

    1. Create a new folder in \nRF5_SDK_16.0.0_98a08e2\examples\ble_peripheral\ble_app_blinky\pca10040\ called s112 to make sure you still have the original project.
    2. Copy all files from \nRF5_SDK_16.0.0_98a08e2\examples\ble_peripheral\ble_app_blinky\pca10040\s132\ into this new folder.
    3. Open the .emproject file with Segger Embedded Studios.
    4. Open the project options in SES and set the build configuration to Common.
    5. Go to Linker, open Section Placement Macros, and change FLASH_SIZE, FLASH_START, RAM_START, and RAM_SIZE to the appropriate values for S112.
    6. Go to Preprocessor, open Preprocessor Definitions and change S132 to S112. 
    7. Open User Include Directories and change ../../../../../../components/softdevice/s132/headers &../../../../../../components/softdevice/s132/headers/nrf52 to ../../../../../../components/softdevice/s112/headers & ../../../../../../components/softdevice/s12/headers/nrf52
    8. Go to Loader (under Debug), open Additional Load File[0] and change this to /YOUR_SDK_FOLDER/nRF5_SDK_16.0.0_98a08e2/components/softdevice/s112/hex/s112_nrf52_7.0.1_softdevice.hex
    9. Compile, build, and run your project, and that should be it.

    Best regards,

    Simon

Children
Related