• State Not Answered
  • Replies 2 replies
  • Subscribers 67 subscribers
  • Views 645 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 234597
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

How sdk upgradation affects bluetooth SIG product declaration?

Deljohn

Hi,
We are working on a product that uses EYSHCNZXZ, nRF52832 based module from Taiyo Yuden. The module is qualified as Component at 'PHY layer only'. The QDID of this module is 81272. It's declared with bluetooth version 4.2 (softdevice 132 V2.0.1). We want to update SDK of the project from nRF5_SDK_11.0 to nRF5_SDK_15.2. But nRF5_SDK_15.2 uses softdevice s132 V6.1.0 which is a bluetooth 5 version.
We know that replacing the SoftDevice will not invalidate the BluetoothRegistered qualification; so if we upgrade to a newer SoftDevice, PHY layer BluetoothRegistered re-qualification is not necessary. But here, the bluetooth version is also changed with new softdevice version, do we have to do something specific for that.

1. Can we use nRF5_SDK_15.2 with Bluetooth 5 on EYSHCNZXZ module and do the product declaration without going for any testing? If yes, can you suggest what we should mention while declaring our product with Bluetooth SIG?

2. With nRF5_SDK_15.2, can we choose not to use bluetooth 5 features and treat it as bluetooth 4.2 device? If possible, how to implement that? and how to approach product declaration with bluetooth SIG?

Our product has both custom services and standard GATT services (Battery Service, Device Information and secure DFU service).

Thanks in advance

Parents
  • 0

    Hi,

     

    1. You can update the Softdevice if you do not make use or enable any new features that are not in the original declaration, meaning you can upgrade to make use of bug fixes and such.

     

    2. You can not use any Bluetooth 5 features and treat the device as Bluetooth 4.2. You might be able to disable Bluetooth 5 features and treat it as 4.2, but I am not sure how this would go, you might have to contact the SIG about this. Technically the SD versions compatible with SDK are Bluetooth 5, even if you do not make use of the 2 Mbps, extended advertising etc. Even though these are the 'main features' of Bluetooth 5 they are actually optional, what decides if a device is Bluetooth 5 or 4.2 is whether or not the erratas from 4.2 have been implemented, and you can not disable these.

     

    Unfortunately this is what might happen when using a 3rd party module. You could contact Taiyo Yuden and ask why they have not released a more up-to-date version (frankly SDK v11 is quite outdated), use another module/manufacturer or make the design yourself.

     

    Best regards,

    Andreas

Reply
  • 0

    Hi,

     

    1. You can update the Softdevice if you do not make use or enable any new features that are not in the original declaration, meaning you can upgrade to make use of bug fixes and such.

     

    2. You can not use any Bluetooth 5 features and treat the device as Bluetooth 4.2. You might be able to disable Bluetooth 5 features and treat it as 4.2, but I am not sure how this would go, you might have to contact the SIG about this. Technically the SD versions compatible with SDK are Bluetooth 5, even if you do not make use of the 2 Mbps, extended advertising etc. Even though these are the 'main features' of Bluetooth 5 they are actually optional, what decides if a device is Bluetooth 5 or 4.2 is whether or not the erratas from 4.2 have been implemented, and you can not disable these.

     

    Unfortunately this is what might happen when using a 3rd party module. You could contact Taiyo Yuden and ask why they have not released a more up-to-date version (frankly SDK v11 is quite outdated), use another module/manufacturer or make the design yourself.

     

    Best regards,

    Andreas

Children
Related