SoftDevice identification and revision scheme

The SoftDevices are identified by the SoftDevice part code, a qualified IC partcode (for example, nRF52832), and a version string.

The identification scheme for SoftDevices consists of the following items:

Table 1. Revision scheme
Revision Description
Major increments

Modifications to the Application Programming Interface (API) or the function or behavior of the implementation or part of it have changed.

Changes as per minor increment may have been made.

Application code will not be compatible without some modification.

Minor increments

Additional features and/or API calls are available.

Changes as per minor increment may have been made.

Application code may have to be modified to take advantage of new features.

Revision increments

Issues have been resolved or improvements to performance implemented.

Existing application code will not require any modification.

Build number increment (if present) New build of non-production versions.
Table 2. SoftDevice revision examples
Sequence number Description
s110_nrf51_1.2.3-1.alpha Revision 1.2.3, first build, qualified at alpha level
s110_nrf51_1.2.3-2.alpha Revision 1.2.3, second build, qualified at alpha level
s110_nrf51_1.2.3-5.beta Revision 1.2.3, fifth build, qualified at beta level
s110_nrf51_1.2.3 Revision 1.2.3, qualified at production level
Table 3. Test qualification levels
Qualification Description
  • Development release suitable for prototype application development
  • Hardware integration testing is not complete
  • Known issues may not be fixed between alpha releases
  • Incomplete and subject to change
  • Development release suitable for application development
  • In addition to alpha qualification:
    • Hardware integration testing is complete
    • Stable, but may not be feature complete and may contain known issues
    • Protocol implementations are tested for conformance and interoperability
  • Qualified release suitable for production integration
  • In addition to beta qualification:
    • Hardware integration tested over supported range of operating conditions
    • Stable and complete with no known issues
    • Protocol implementations conform to standards