• State Verified Answer
  • Replies 2 replies
  • Subscribers 68 subscribers
  • Views 3334 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 238075
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Migration - nRF52832 > nRF52833 Code compability

Ask C.

Hi,

Say we want to migrate from the nRF52832 that we're using currently to the nRF52833, what are the implications, i.e. are they "code compatible"?

Br, Ask.

Parents
  • +1

    You'll have to migrate to SDK16.0 as it is the only SDK with support for the 52833. The code will be almost identical for 52833 as for 52832, with the exception of some startup files, bitfields header file, and bugfixes specific for 52832 and 52833. The bugfixes are handled by the drivers or HAL's, and you as a programmer do not need to worry about them. The same goes for startup and header files. 

    Pick an example that targets the nRF52833 and import the code you need and modify the sdk_config.h file to match, if you've already migrated the nRF52832 code to SDK16 it should now compile with the nRF52833 as the target. 

    Do note that the nRF52833 DK will have different GPIO pin mappings compared to the nRF52832 DK.


Reply
  • +1

    You'll have to migrate to SDK16.0 as it is the only SDK with support for the 52833. The code will be almost identical for 52833 as for 52832, with the exception of some startup files, bitfields header file, and bugfixes specific for 52832 and 52833. The bugfixes are handled by the drivers or HAL's, and you as a programmer do not need to worry about them. The same goes for startup and header files. 

    Pick an example that targets the nRF52833 and import the code you need and modify the sdk_config.h file to match, if you've already migrated the nRF52832 code to SDK16 it should now compile with the nRF52833 as the target. 

    Do note that the nRF52833 DK will have different GPIO pin mappings compared to the nRF52832 DK.


Children
Related