Skip to main content

SDK for BT4.2

4 years ago

SDK for BT4.2

Posted byzwang3080 points 12 replies
0 upvotes

Hi Dialog,

I am developing BT software for DA14580 base on SDK 5.0.3. Am I in BT 4.2 world? Is there any method for me to check my BT stack version?

谢谢s a lot!

4 years ago

MT_dialog -30 points

Hi zwang308,

Please check the below post

http://support.dialog-semiconductor.com/da1458x-qualified-42

谢谢s MT_dialog

4 years ago

zwang308 0 points

Hi MT_dialog,

谢谢s a lot for your answer.

What I am curious about is:

I know there are some difference between BT 4.0 and 4.2 e.g. MTU size, security staff...

I was using DA14580 and SDK3. That is BT4.0.

Currently I am using DA14580 and SDK 5.0.3. Am I running BT 4.2 now?

I saw some information on this forum saying you are still on SDK support for BT 4.2 on DA14580 and is was posted on Apr 2016. However, SDK 5.0.3 was published on Oct 2015. So I am assuming although DA14580 is qualified for BT4.2, using DA14580 and SDK 5.0.3 will not take all advantage of BT 4.2? Is that correct?

谢谢s a lot.

4 years ago

MT_dialog -30 points

Hi zwang308,

Thats right, the stack of the 580 supports only the mandatory features of the 4.2 specification and not the optional ones.

谢谢s MT_dialog

4 years ago

JE_Dialog

Hi Zwang308, we launch the DA14680-01 end of July : this will support optional features of 4.2. Please keep an eye on the support site - everything should be accessible later in July . BR JE_Dialog.

4 years ago

zwang308 0 points

Hi Dialog,

谢谢s a lot for your answers and I am really appreciated. Due to the package size and target date issue, we have to use DA14580 at this point of time.

Could you please help me to check whether these three BT4.2 features are support by DA14580:

1. Larger PDU: In 4.2 one can send much larger data packets. This will be very important to increase throughput for the firmware update.

2. Secure Simple pairing: Key exchange to derive LTK is done with Elliptic Curve Diffie-Hellman.

3.配对后数值比较。

谢谢s a lot for your help.

4 years ago

MT_dialog -30 points

Hi zwang308,

1. The data packet length extension is a new feature introduced in 4.2 and not supported.

2. You mean LE Secure Connections pairing that also a 4.2 new feature, and not supported.

3.I dont get the last one, the numeric comparison association model is feature of the 4.0 specification, if that is what you mean.

谢谢s MT_dialog

4 years ago

zwang308 0 points

Hi MT_Dialog,

Is there any plan of releasing a new SDK to support these feature on DA14580? Do we have any date of that?

If not, is there any possible to use BT4.2 with BT4.2 new features(at least all features I listed above) on DA14580?

谢谢s a lot!

4 years ago

MT_dialog -30 points

Hi zwang308,

A Dialog's local team member will contact you regarding your request.

谢谢s MT_dialog

2 years ago

jetsonindustries 0 points

Hey Team,

Was there a recent update to this article? Does the DA14680 support the data packed length extension in BLE4.2?

If so, would it be possible for someone to share some details of how we can do the upgrade from 4.0 to 4.2 to take advantage of this feature?

谢谢s,
Ben

2 years ago

JE_Dialog

Hi Ben, DA1468x family supports all the features (including optional) of 4.2, which does include PLE. This feature is available within the SDK .

Additionally, we now have the DA14682/3 wihch are supporting all core and supplemental features of 5.0.

BR JE_Dialog

2 years ago

jetsonindustries 0 points

谢谢s for the quick reply!

This is great news, we'll research the new models.

Are there any tutorials or documentation on how to update to 4.2 and bring in the data packet length extension feature?

2 years ago

PM_Dialog

Hi Jitendraprasad,

The Data Length Extension feature is included to the last version of SDK. You are able to download the tatest version of the SDK from our support page. Please follow the steps below:

  1. In the ble_config.h header file:

#define dg_configBLE_DATA_LENGTH_RX_MAX(251)

#define dg_configBLE_DATA_LENGTH_TX_MAX(251)

According to the BLE specifications, you are able to send 251 bytes max in one packet. Be aware that the maximum size of the packet is related to SIG specifications and power consumption.

  1. Use the ble_gap_mtu_size_set() API from ble_gap.h header file in order to set the MTU size that you want. Be aware that you have to call this function before the initialization of the attributes database. Otherwise, the database will be erased.

Please, let me know if you want further guidance.

谢谢s, PM_Dialog