- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Who provides a “Host Subsystem” QDID for Infineon based WiFi/BT modules that run a WICED stack?
A “Host Subsystem” QDID is required to complement the “Controller Subsystem” QDID that is provided by Murata for their 1DX module. Infineon appears to only provide a “Component” QDID for the WICED software stack.(2) (3)
Bluetooth Certification requires either a single "End Product” QDID or combined “Controller Subsystem” and “Host Subsystem” QDIDs.(1).
CYW4343x = QDID: 134532 – Component @ https://launchstudio.bluetooth.com/ListingDetails/89357
Murrata 1DX = QDID 140301 - Controller Subsystem @ https://launchstudio.bluetooth.com/ListingDetails/96389
WICED Stack = QDID 115853 – Component @ https://launchstudio.bluetooth.com/ListingDetails/65279
References:
- Bluetooth Module Vendor Qualification Guide @ https://www.bluetooth.com/develop-with-bluetooth/qualification-listing/module-vendor/
- QDID: 115853 is Component (Tested) per “WICED Studio and ModusToolbox Bluetooth Stack QDID” @ https://community.cypress.com/t5/ModusToolbox-Bluetooth-SDK/WICED-Studio-and-ModusToolbox-Bluetooth-...
- QDID:160340 is Component (Tested) per “Can WICED use new QDID ?” @ https://community.cypress.com/t5/WICED-Studio-Wi-Fi-Combo/Can-WICED-use-new-QDID/m-p/165516
A similar question is posted on Murata’s website:
Greg
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The table below shows two QDID paths that can be used to leverage a BT SOC supplier or Module partner's existing BT Certification in a new design. We support option 1 by providing Component QDIDs, some Module Partners support option 2 by providing Subsytem QDIDs. Note that the Profiles QDID for the component listing can sometimes be excluded as the embedded host contains profiles within the Host QDID. I always recommend that customers work with their BT Sig POC to confirm their selection prior to filing.
No |
Controller |
host |
Profiles |
1 |
Component |
Component |
Component |
2 |
Subsystem |
Subsystem |
Subsystem |
Note that our MT BT SDK BT 5.2 stack listing is complete:
Based on the dialog above, one would use QDID 160340 (Host/Component) with QDID 134532 (Controller/Component) to leverage our BT Cert with the Murata 4343W based module.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The table below shows two QDID paths that can be used to leverage a BT SOC supplier or Module partner's existing BT Certification in a new design. We support option 1 by providing Component QDIDs, some Module Partners support option 2 by providing Subsytem QDIDs. Note that the Profiles QDID for the component listing can sometimes be excluded as the embedded host contains profiles within the Host QDID. I always recommend that customers work with their BT Sig POC to confirm their selection prior to filing.
No |
Controller |
host |
Profiles |
1 |
Component |
Component |
Component |
2 |
Subsystem |
Subsystem |
Subsystem |
Note that our MT BT SDK BT 5.2 stack listing is complete:
Based on the dialog above, one would use QDID 160340 (Host/Component) with QDID 134532 (Controller/Component) to leverage our BT Cert with the Murata 4343W based module.