NRF5340 SoftDevice Controller reports different version than NRF5340 QDID matrix

Hello,

I noticed that the SoftDevice Controller for nrf5340 in nrf Connect SDK 3.1.0 reports a bluetooth version of 6.1 (LMP Version 0x0F), yet the QDID for it (Q360820) is listed as using Core Spec 6.0.

Do the versions need to match? 

Is it an issue for Bluetooth certification where a listing declares compatibility with a certain Core-Spec version, say 6.0 to match the version documented in Nordic's NRF5340 QDID matrix, yet the controller component declares it supports a later version via LL_VERSION_REQ/IND?

Parents
  • Got the reply from the team:

    The QDID got filed with BT6.0 on release ncs3.0.x with a defined "feature set" / functionality.

    As long as the feature set does not change the QDID is also valid for  bug-fixes-versions and newer ncs versions. That the SW reports that it can cope also with the newer BT-version should not matter, because it is still conform (backwards compatibility) with the filed QDID on BT-6.0

    As long as the device is reporting the correct feature set over the air, the core spec version doesn't really hold any significance anyway.  So from the SIG viewpoint, this should not be an issue.

Reply
  • Got the reply from the team:

    The QDID got filed with BT6.0 on release ncs3.0.x with a defined "feature set" / functionality.

    As long as the feature set does not change the QDID is also valid for  bug-fixes-versions and newer ncs versions. That the SW reports that it can cope also with the newer BT-version should not matter, because it is still conform (backwards compatibility) with the filed QDID on BT-6.0

    As long as the device is reporting the correct feature set over the air, the core spec version doesn't really hold any significance anyway.  So from the SIG viewpoint, this should not be an issue.

Children
Related