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

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
  • Hi Ali

    There should not be any "migration" necessary to change the SoftDevice on your application. What project are you trying to run with the S112 SoftDevice? What problems are you having? The main reason people usually have trouble is that the S112 has a few limitations compared to S132. First off, the S112 can not be a central, so you will not be able to run a project with a central on the S112 SoftDevice. Next, the S112 does not support Extended advertising, L2CAP with LE Credit-based Flow control, and LE data packet length extension, so if you try running a project with these features with S112 you'll likely experience some errors.

    If your project supports using S112, you should be able to compile, build and flash the project to your device along with the SoftDevice without any trouble.

    Best regards,

    Simon

Reply
  • Hi Ali

    There should not be any "migration" necessary to change the SoftDevice on your application. What project are you trying to run with the S112 SoftDevice? What problems are you having? The main reason people usually have trouble is that the S112 has a few limitations compared to S132. First off, the S112 can not be a central, so you will not be able to run a project with a central on the S112 SoftDevice. Next, the S112 does not support Extended advertising, L2CAP with LE Credit-based Flow control, and LE data packet length extension, so if you try running a project with these features with S112 you'll likely experience some errors.

    If your project supports using S112, you should be able to compile, build and flash the project to your device along with the SoftDevice without any trouble.

    Best regards,

    Simon

Children
Related