• State Not Answered
  • Replies 1 reply
  • Subscribers 64 subscribers
  • Views 29 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 330666
Options

Migrate from nRF52832 to nRF52833

mikefraguglia

Hello, we currently use nRF52832 in our product. For the next generation of this product, we are hoping to upgrade to a new module that uses nRF52833. However, this is only practical if we can use our existing codebase without significant modification.

We use nRF52 SDK v15.3.0 and S132 SoftDevice v6.1.1.

What modifications to our code might be required, if any?

Parents
  • 0

    Hi,

    To switch between nRF52832 and nRF52833, you need to rebuild the application for the correct chip variant, and switch to a compatible SoftDevice version.

    Support for nRF52833 was first introduced in nRF5 SDK v16.0.0, as you can see from the nRF52833 SDKs and SoftDevices compatibility matrix. Additionally, S132 softdevice is not supported/qualified for use with nRF52833, you will need to switch to S140 or S113 softdevice variants.

    You can have a look at the Migration guide for nRF5 SDK v16.0.0 to see if the workload is something you can overcome, but it will definitely require some work to switch between these two chip variants.

    Best regards,
    Jørgen

Reply
  • 0

    Hi,

    To switch between nRF52832 and nRF52833, you need to rebuild the application for the correct chip variant, and switch to a compatible SoftDevice version.

    Support for nRF52833 was first introduced in nRF5 SDK v16.0.0, as you can see from the nRF52833 SDKs and SoftDevices compatibility matrix. Additionally, S132 softdevice is not supported/qualified for use with nRF52833, you will need to switch to S140 or S113 softdevice variants.

    You can have a look at the Migration guide for nRF5 SDK v16.0.0 to see if the workload is something you can overcome, but it will definitely require some work to switch between these two chip variants.

    Best regards,
    Jørgen

Children
No Data
Related