Hi Renesas's Guys
in my company we developed a product equipped with DA14531MOD.
The firmware used is based on DSPS (https://www.renesas.com/us/en/software-tool/serial-port-service-sps) with just a couple of modifications to adapt it to our needs.
All modification are only in UserApplication. No modification in SDK or bluetooth stack.
Now we are in release stage and we are approaching Bluetooth Product Registration.
In DA14531MOD datasheet I can find QDID subsystems for host, controller and profiles.
But during the listing process it is no possible to include QDID for profile subsystem because it reference to withdrawn specification (https://launchstudio.bluetooth.com/ListingDetails/94761).
Here my questions:
Hi There,Thank you for posting your question online.Let me try to answer your questions:
HTItaliaSrl said:because in DSPS application is used only the GATT-based profiles (as stated in par 4.3 of DSPS user manual https://www.renesas.com/us/en/document/mat/um-b-088-da145x-user-manual-dialog-serial-port-service ) can we use only the QDIDs for controller and host subsystems?
You should use the QDIDs for controller, profiles and host subsystems. Please refer here as well: Qualify Your Product | Bluetooth® Technology WebsiteAt the bottom of the page you can find:
HTItaliaSrl said:If in the future we would use a specific profile (HRP, TIP, ANP, ...) have we to redo (and pay again) the product registration process?
If you change only the Firmware of your board then there will be no need for further registration. If you make changes on the Hardware that could possibly affect the radio performance then you will need to redo the registration process.
HTItaliaSrl said:Just to include a backdoor to use specific profile, can QDID 149894 and 165047 for profile subsystem (qualified and registered by Dialog/Renesas) be used also if they are not referenced by DA14531 datasheet?
Yes, you can do that. As you can see on the DA14531 QDID Profile SubsystemThe DA14531MOD is covered by this QDID. Same thing applies for the QDID 149894.Generally, when you design a new product, you will need to get the qualification/certification via the Testing facilities that are recognized by Bluetooth SIG. This happens because, on your custom board you might have affected the Radio performance and it might not fit in the specification of Bluetooth. However, the DA14531MOD is a module that has an integrated Antenna and SPI Flash. As long as you have placed the DA14531MOD correctly on your custom board you should be good to pass the Certification process. Best Regards,OV_Renesas
following are my comments
OV_Renesas said:You should use the QDIDs for controller, profiles and host subsystems. Please refer here as well: Qualify Your Product | Bluetooth Technology WebsiteAt the bottom of the page you can find:
OK, but the QDID referred in the datasheet is unusable (because it reference to withdrawn specs). And the other ones are not noticed in the datasheet.
So, I'm wondering if the best is to use only QDID for HOST and CONTROLLER because in our actual application (and probably also in the future) we are NOT using any of Application Specified Profile.
BTW, in your opinion, what if I include the only valid QDID for profile 149894 (just for Interoperability Test Specification supported layer) but the real application "uses" only host and controller QDID?
Hi There,Thank you for the reply.
HTItaliaSrl said:So, I'm wondering if the best is to use only QDID for HOST and CONTROLLER because in our actual application (and probably also in the future) we are NOT using any of Application Specified Profile.
If your application is not going to use any of the Specific Profiles that have designated assigned numbers by Bluetooth SIG then there is no issue/reason to submit the QDID for Profile subsystems.
HTItaliaSrl said:BTW, in your opinion, what if I include the only valid QDID for profile 149894 (just for Interoperability Test Specification supported layer) but the real application "uses" only host and controller QDID?
I do not believe it will be an issue. They might ask you if you have any firmware version that also uses designated Profiles or if you intent to have on the future. Best Regards,OV_Renesas
I did the same question to our FAE that is in touch with Application Layer from Renesas and they gave us more or less the same answer, but with a phrase that I don't understand.
They state that:
"Customer usually do not refer to our Profile QDID because the qualification needs to be done on the application layer plus the service. Because of this we do not update the profile QDID for every new SDK release.
The reason why we publish the QDID 138960 is to show customers, our profiles are qualifiable.
Best is to purchase the 50euro qualification USB dongle and run the PTS
What's the scope of PTS?
Seems that I can go through declaration process using only QDID for host and controller and, if in a future case, run PTS to add to our declaration WITHOUT pay anoter fee.I'm right?
Hi There,Thank you for the reply.PTS need to test their application to be compliant to SIG spec in case you include profiles in your application because you will need to qualify the whole application in this case.Best Regards,OV_Renesas