My question is very similar to If I use nrf Connnect SDK 1.6.1 and Zephyr, which Bluetooth QDID should I use?
Following this case I need Zephyr Version 2.2.x and can use QDID 151074 (Demant A/S)
What nrf Connect Version do I have to use to work with Zephyr Version 2.2.x? Is there a table with nrf Connect versions - Zephyr Versions and QDIDs?
What is the latest Version of nrf Connect that supports a Zephyr Version with a valid QDID
Thanks for support
Please note that the nRF Connect SDK is based on the Zephyr RTOS. So as soon as you use nRF Connect SDK, you do also have Zephyr RTOS included. And based on the KCONIFG settings in your project the exact feature set is defined.
This is also true for the Bluetooth software. The older nRF5 SDK used a binary library that included the whole Bluetooth stack. This binary was offered as a dedicated SoftDevice version. Don't mix this up with the SoftDevice Controller that is used in nRF Connect SKD. This one is only the Bluetooth Link Layer (the whole bluetooth stack consist of Bluetooth Link Layer or also called Bluetooth Controller and the other part is the Bluetooth Hoss).
For Bluetooth End Product Listing (EPL) you should usually mention three parts:
1) nRF52 PHY (e.g. for the nRF52832 you find the QDID on the bluetooth.com webpage:
https://launchstudio.bluetooth.com/ListingDetails/115770
or use the search on the bluetooth.com / Find a Product webpage:
https://launchstudio.bluetooth.com/Listings/Search
)
2) Bluetooth Host: here is only one version existing. And the QDID for the host subsystem can be found in table 2 on this page:
3) Bluetooth Controller: the default setting in nRF Connect SDK is usually to use the SoftDevice Controller. the QDID can be found in table 2 on following page:
Please note that the nRF Connect SDK is based on the Zephyr RTOS. So as soon as you use nRF Connect SDK, you do also have Zephyr RTOS included. And based on the KCONIFG settings in your project the exact feature set is defined.
This is also true for the Bluetooth software. The older nRF5 SDK used a binary library that included the whole Bluetooth stack. This binary was offered as a dedicated SoftDevice version. Don't mix this up with the SoftDevice Controller that is used in nRF Connect SKD. This one is only the Bluetooth Link Layer (the whole bluetooth stack consist of Bluetooth Link Layer or also called Bluetooth Controller and the other part is the Bluetooth Hoss).
For Bluetooth End Product Listing (EPL) you should usually mention three parts:
1) nRF52 PHY (e.g. for the nRF52832 you find the QDID on the bluetooth.com webpage:
https://launchstudio.bluetooth.com/ListingDetails/115770
or use the search on the bluetooth.com / Find a Product webpage:
https://launchstudio.bluetooth.com/Listings/Search
)
2) Bluetooth Host: here is only one version existing. And the QDID for the host subsystem can be found in table 2 on this page:
3) Bluetooth Controller: the default setting in nRF Connect SDK is usually to use the SoftDevice Controller. the QDID can be found in table 2 on following page:
