About the new SDK (1.0.12.1078) for DA1468x

⚠️
Hi there.. thanks for coming to the forums. Exciting news! we’re now in the process of moving to our new forum platform that will offer better functionality and is contained within the main Dialog website. All posts and accounts have been migrated. We’re now accepting traffic on the new forum only - please POST any new threads at//www.xmece.com/support. We’ll be fixing bugs / optimising the searching and tagging over the coming days.
3 posts / 0 new
Last post
Wed, 2017-12-27 09:57
#1
Jun-ichi Tobe
Offline
Last seen:5 months 4 weeks ago
加入:2016-04-01 10:39
About the new SDK (1.0.12.1078) for DA1468x

Hello support team.

Regarding the new SDK released on December 20, I have 5 questions as follows.

1) About connectivity with BT 5.0 equipment
Description : "Improve interoperability of BLE with other implementations."
Are there anything wrongs with connectivity with BT 5.0, if I do not apply this new SDK?
Also, could you please provide what kind of connectivity has improved?

2) About connection-oriented
Description : "Added checks for valid connection in connection - oriented There is BLE GATT API functions."
Could you please provide what kind of additional content?

3) Necessity of replacement
The OverView in 1.0.10 and 1.0.12 has the following description.
It seems to be the difference between easily and directly.
What are the differences? Is it possible to replace the SDK more easily with the new SDK?
Description :
>>[1.0.10]
>>All existing APIs have not changed; projects developed on release 1.0.8 should be ”easily" portable to 1.0.10.
>>[1.0.12]
>>All existing APIs have not changed; projects developed on release 1.0.10 should be "directly" portable to 1.0.12.

4) About SUOTA specification
Could you please tell me what specific improvements are on the following contents in "Fix / Improvement item"?
Description :
Fix for Software Upgrade background operations failing to execute ERASE if interrupt occurs just before the operation starts.

5) About Charger specification
I think the charge function was implemented in SDK 1.0.10 with the following contents in "Fix / Improvement item".
你能告诉我们什么样的进步?
Description :
State of Charge API fixed so that it can also be enabled with rechargeable batteries

Regards.

Jun-ichi

Device:
DA1468x
Thu, 2018-01-11 16:48
Jun-ichi Tobe
Offline
Last seen:5 months 4 weeks ago
加入:2016-04-01 10:39
Hi Support　Team!

Hi Support　Team!
Would you please reply as soon as possible about the information on the SDK difference？
Best regards.

Jun-ichi

Fri, 2018-01-12 17:03
(Reply to #2)
MT_dialog
Offline
Last seen:2 months 1 week ago
Staff
加入:2015-06-08 11:34
Hi Jun-ichi Tobe,

Hi Jun-ichi Tobe,

Mentioning at the forum the exact changes and differences between the two SDKs its not possible and its not possible to document all the changes that are made between the two SDKs in detail also tracing back all the changes that are under a specific title like "fix interoperability issues" is also not possible since that might include more than one fix. I have managed to gather a few comments from the team, hope that will help you on your request:

  • About Connectivity of BT 5.0 equipment, its more like a generic comment, including minor fixes including procedures, improvements in profile implementation etc.
  • About connection oriented, a series of extra checks in the BLE manager GATT handlers regarding the connection status (i.e return BLE_ERROR_NOT_CONNECTED when the connection has been dropped).
  • Regarding the necessity of replacement, i dont think that there is a difference between the easily and directly, both of the SDK's can be ported as easy.
  • Regarding the SUOTA specification, there was an issue with the erase command when the device was during idle state and the background ops were about to operate if there was an erase command to be executed by the background operations and an interrupt occured (any interrupt) the system would go and serve the interrupt and when done executing the interrupt the device would not execute the erase command.
  • Regarding the state of Charge a correction is made to the code since during building a when the user was selecting BATTERY_TYPE_NO_BATTERY.

Thanks MT_dialog