nRF52832 revision 1 with SDK 16

[bart]

Hi,

I looked at https://infocenter.nordicsemi.com/topic/comp_matrix_nrf52832/COMP/nrf52832/ic_rev_sdk_sd_comp_matrix.html and I was wondering if the nRF52832 rev 1 does not work with SDK 16.

I read somewhere else that it's because newer SDKs assume PANs to be fixed, but the list of fixed PANs of rev 2 isn't that long: https://infocenter.nordicsemi.com/index.jsp?topic=%2Ferrata_nRF52832_Rev2%2FERR%2FnRF52832%2FRev2%2Flatest%2Ferr_832_fixed.html

[Susheel Nuguru]

Hi bart,

It is a good question and you are correct in your understanding.

Normally when we release an SDK, we have some header and source files that we import from a certain nRF MDK. This imported files are based on nRF MDK releases that have maintained startup files for each device variant. The MDK startup files for nRF52832 in the SDK16 have removed few PAN workarounds that are fixed for Rev 2. 

Also, SDK16 works only with SD7.0.1 which have also removed some of the workarounds as this version of SD is officially supporting  Rev2 silicon. Because of this dependency of SD version on SDK and SDK depending on the particular version of MDK files, hence this dependency.

Applying the workarounds in the app are not that simple, since some workarounds are applied inside the SoftDevice at certain instances not easily accessible to the application.

[bart]

So that means that revision 1 won't get new SDKs anymore? I hope that isn't going to be the case for all software kits (like the mesh SDK), as we would like to keep improving the software for older products as well.

[Susheel Nuguru]

Yes, ERRATA 102, 106 and 107 are related to RADIO that are fixed in revision 2. So these errata fixes are removed from the softdevices versions that is the requirement for SDK 16 onwards. So unfortunately you cannot use Rev1 with newer SDK's-