Post:
Hi Nordic Team,
We are currently developing a product based on the Raytac MDBT50Q-1MV2 module, which integrates the nRF52840 SoC. Our firmware is built using the nRF Connect SDK (NCS), currently version 2.8.0, with plans to upgrade to 3.0.1.
We are preparing for Bluetooth SIG qualification. Raytac provides a qualified design with QDID 232392 for their module, which references Nordic’s QDID 228005 (based on NCS 2.4/2.5). However, they have not yet qualified a design based on SDK 2.8.0 or 3.0.x.
I have a few questions regarding the qualification process:
-
Use of Nordic DNs with Raytac Module:
Given that Nordic has more recent Declaration IDs (e.g., Q358851, Q360820 for SDK 3.0.x) listed for the nRF52840 (as seen in your documentation), is it possible to use one of these newer DNs to qualify a product that uses the Raytac MDBT50Q-1MV2 module, instead of relying on Raytac’s QDID 232392? Are there any downsides or limitations to this approach? -
Use of Standard GATT Services (DIS, BAS):
We are using standard services such as the Battery Service (BAS) and Device Information Service (DIS) as implemented in the nRF Connect SDK. These are not custom services and do not introduce any additional X.2 Core profiles. If we use Nordic’s DN, do we need to declare our design “with modification,” or are these services already covered under Nordic’s qualified designs? -
Impact of SDK Updates on Qualification:
If we initially qualify our product using SDK 2.8.0 and later update to SDK 3.0.x (for which Nordic provides new DNs), would we need to perform a new qualification or adoption each time we update the SDK? Would such an SDK update incur additional qualification costs?
Our goal is to ensure that our qualification aligns with the SDK version we are using, while still leveraging the pre-certified module.
Any guidance on how to proceed with this approach would be greatly appreciated.
Thanks.
Best Regards
Marvin