Bluetooth SIG listing when upgrading from S110 to S130

[Sergey Tcherednichenko]

Hi!

We have several products which use SoftDevice S110, some of them are already in production and are listed as Bluetooth Qualified, some of them we are preparing for production and listing now. We were considering to upgrade to SoftDevice S130 (both existing and new products).

For existing products - it's quite clear that we would need to pass Bluetooth Qualification once again. But for the new products - may we choose the Core specification 4.2 for them from start, even if we are going to roll them out with S110 (which is a qualified Bluetooth 4.1 component) first, and then upgrade? Or would we still need to choose Core spec 4.1 and then update the listing?

Also, the problem is that the firmware upgrade would be done OTA, so we can't specify the exact moment when every single device would receive the new firmware.

Best regards,

Sergey

[run_ar]

Hi,

The requirement to re-qualify your product only applies if you change it. In the context of Bluetooth qualification this means changing the PIXIT / ICS document.

So when updating from S110 to S130 you do not have to declare your product again unless you use the new features available in S130. If you use any of the new features, the pixit will change and you will have to declare your product again.

In the second case, where you know you will be using S130, but some products will have the S110 until they are updated, you should list your product based on the S130. It is ok to only use a subset of features (That is what most people do when referencing a qdid for a ble stack as the stack more often than not has features not used by the application).

Br,