Nordic Team,
Is it safe to upgrade SDK 12.2.0 to S132 V3.1.0? If so why was this minor update left out of the SDK release?
Thanks, Darren
Nordic Team,
Is it safe to upgrade SDK 12.2.0 to S132 V3.1.0? If so why was this minor update left out of the SDK release?
Thanks, Darren
Hi Darren,
There should be no problem updating to S132 v3.1.0 with SDK 12.2.0. SDK 12.2.0 was released on Desember 6., while S132 v3.1.0 was released later, on Desember 7. As this is just a small update, with no changes to the API, no effort were put into integrating it to SDK 12.2.0. It should be straight forward to switch to the latest softdevice.
Best regards,
Jørgen
Jorgen,
Thanks for the update.
Also, think I may have found a bug in two of the S132 V3.1.0 header files.
nrf_nvic.h and nrf_soc.h have the following define #ifdef NRF52
but the header files from the SDK 12.2.0 have this define #if (defined(NRF52) || defined(NRF52840_XXAA))
. The NRF52 define seems old when I review the nrf.h from SDK 12.2.0 which defines NRF52_SERIES
.
Darren
I think the header files in SDK 12.2 have been altered to allow using S132 softdevice with the new nRF52840 PDK. There will soon be released a new softdevice (S140) for use with nRF52840. I guess there will be a better cleanup in the next SDK, when there are separate softdevices for each device. If you want to use S132 v3.1.0 with nRF52840 PDK, you will need to modify the header files as well. With nRF52832, it should work without modifying the header files.