• State Verified Answer
  • Locked Locked
  • Replies 2 replies
  • Subscribers 88 subscribers
  • Views 1030 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 269977
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Migrate softdevice from S132 to S113

kosme

Due to the recent semiconductor global shortage, we are changing the chip on our device currently on the market from the nRF52832 chip to the newer nRF52833. I am in charge of the migration and opted for using the softdevice S113 as it is compatible with both chips which will allow to continue developing code that will be functional on both the old devices and the new ones

I am using GCC 10.2.1 and SDK 7.0.2

I already changed the headers on the Makefile, along with flashing the new softdevice and the code is compiling correctly but it is not running.

What other changes/modifications am I probably missing?

  • 0

    You must elaborate on "not running" in order to get help here.

    Hook up a j-link debugger, look where code execution ends up.

  • +1

    Remember the S113 is a peripheral only Softdevice so you should not be using the central role on the S132.
    These are the suggested steps.

    Step 1: Read the migration guides that are present in the Softdevice release folders, they are usually located at 
    nRF5_SDK_17.0.2_d674dde\components\softdevice\s132\doc\s132_nrf52_7.2.0_migration-document.pdf
    nRF5_SDK_17.0.2_d674dde\components\softdevice\s113\doc\s113_nrf52_7.2.0_migration-document.pdf

    Step 2: Move the S132 and the SDK that you are using to the latest version of the SDK which is SDK 17.0.2 and the S132 v7.2.0, this will prepare you to switch to the S113 v7.2.0

    Step 3: Switch your nRF52832 current development to S113 v7.2.0 and verify

    Step 4: Switch your development to the nRF52833 with SDK v17.0.2 and S113 v7.2.0

    The steps are a bit long but it will keep the number of simultaneous changes to a minimum and a better probability of a successful migration. Verify each step before continuing.

Related