QDID used during BLE authentication with third-party modules

Hello

I am attempting to perform BLE certification using a third-party module for the nrf52832.

Should I select the nRF Connect SDK QDID for all design items?

Or, should the RF-PHY item select the QDID of the BLE module?

The modules used are as follows:

  • Fanstel BM832 (QDID:97989)
  • nRF Connect SDK 2.6.1

The QDID for BM832 is from S132 v5.0.0, but I am using nRF Connect SDK 2.6.1.

Regarding BLE certification, will testing be required?

Thank you.

Parents Reply
  • Hi ReoN,

    I can't access the QDID search now, so I cannot confirm that numbers are the correct one.

    You can select the module's QDID number for RFPHY.

    For the other parts, they are not all the same number. Notice that the LL part has to use the QDID number for the SoftDevice Controller, and the L2CAP and GATT parts have to use the QDID number for the nRF Connect SDK Host Subsystem.

Children
  • Hello Hieu,

    Are there no changes to the Link Layer in the upgrade from S132 v5.0.0 to nRF Connect SDK 2.6.1?

    Is it acceptable to assign the same QDID as RF-PHY even if there are changes to the Link Layer?

    Thank you.

  • Hi ReoN,

    The Link Layer is a part of the Bluetooth LE Controller, not the RFPHY layer.

    You do need to use the QDID of the default Bluetooth LE Controller in NCS, which is named "SoftDevice Controller"
    You must not use the one for the S132 v5.0.0.

    While the term "SoftDevice Controller" and "SoftDevice" sound similar, they refer to two different things.
    SoftDevice is a part of the nRF5 SDK solution. The component S132 or S140 are different SoftDevices with different capabilities and compatibilities with different SoCs.
    A SoftDevice Controller is a part of the NCS solution. It is the Bluetooth LE Controller there.

    Hieu

  • Hello Hieu,

    I understand that only RFPHY is assigned the QDID s132, while the others use the QDIDs of the SoftDevice Controller subsystem and Host subsystem.

    Thank you.

Related