Hello,
I am working with a customer that used a Murata Type ZY. They've voiced concerns that their initial development was done back when the SDK supported up to BT4.1 and they may need to update their firmware to BT4.2. This has caused a lot of questions to arise regarding the process. Murata refers to the Type ZY as a BT4.1 module (https://wireless.murata.com/eng/雷电竞官网登录products/rf-modules-1/bluetooth/type-zy....) so it is presumed that this module was originally developed back when the DA14580 was only BT4.1 compliant. I've read threads that state that Dialog handles ROM patching (https://support.dialog-semiconductor.com/how-do-use-patch-thanks), and that any 14580 device can support 4.0, 4.1, or 4.2 but what matters is the version of SDK used to develop your application code. So that would mean that any changes to make the device 4.2 compliant would not be in ROM but rather, a software fix.
All of this having been said, I have these questions:
1) Is there an app note that describes the migration process from BT 4.1 to 4.2 for the DA14580?
2) My customer has units in the field that are currently BT4.1. Is it possible to update these devices to be 4.2 compliant or do they need to scrap those units because of OTP?
Thank you.
Hi michael.stevens,
The DA14580 chip is qualified to the BLE4.2, which means that it can connect with other devices that supports BLE4.2. Also, be aware that the rom of the DA14580 supports BLE4.2, but the SDK does not supports all the features yet. So, they are not needed any changes/configurations from 4.1 to 4.2.
Thanks, PM_Dialog
I thank you for the response but it's missing something. A chipset can support BT4.2 but only if the application is developed using an SDK that supports 4.2.
SDK revisions, as they release, support later versions of Bluetooth LE. If their application was developed using an SDK that was released prior to the SDK that supported BT4.2 and they've since programmed devices with the binaries generated from the SDK that didn't support the required errata to bring it up to 4.2 compliance, are they able to rebuild their application using the latest SDK to bring it up to 4.2 compliance? If they've programmed devices using the application binaries from the older SDK, can the devices be re-programmed using the new binaries? I suspect that the OTP is true OTP and so once they're programmed once, there is no re-programming.
Please confirm.
Hi michael.stevens,
Let me ask you some questions first to get more information about their issue.
Please, be aware that the version number for the BLE stack is not configurable in the SDK level of the DA14580 SDK, because it is coming from LL layer. Therefore even if they upgrade their SDK software the rom will still be 4.1 compliant.
Thanks, PM_Dialog
Ok so it would seem that I've misinterpreted some of the information out there as I was under the impress that there have been no ROM revisions to support newer Bluetooth revisions, just patches included in the SDK that get mirrored into RAM.
I was under the impression that the software work had already been done but that information was misrepresented. Assemblies have been built but none of them have been programmed yet. I think my next step is to get module revision information from the customer that I can then correlate to DA14580 silicon revisions, which should correlate to ROM revisions, correct?
Hi michael.stevens,
Yes, it would be very help to get more information from your customer. Please ask them about the SDK version and when the product released for the first time in the market.
Thanks, PM_Dialog