BLE Data Length Extension Usage and Example

RE: BLE Data Length Extension Usage and Example

AHaug — Thu, 28 Apr 2022 08:23:01 GMT

Hi Pam,

[quote user="AHaug"]2) I will look closer into this tomorrow and come back with a reply then.[/quote]

The short answer is: Yes, the proj.conf file overrides the configurations from the Kconfig.

The longer answer that might go a bit out of the scope is: Yes they do as long as they are defined in the Kconfig. Most of our samples has a proj.conf that enables/overwrites Kconfigs that are set elsewhere. If you inspect "CONFIG_BT_CENTRAL=y" in proj.conf for throughput, it takes you to the Kconfig located at "C:\peripheral_uart\zephyr\subsys\bluetooth\Kconfig" and this is what it enables and/or overwrites. If a configuration is not defined anywhere in the stacks/SDK/toolchain etc, you may not define a new custom configuration such as "CONFIG_NORDIC_EXAMPLE=y" here.

But you may add your own custom Kconfig to the application located in your application folder where you may define such custom macros and values etc, in a similar manner such as what is done in the Kconfig for bluetooth at the path mentioned above. If you do so, then you may overwrite it in the proj.conf file for your application.

[quote user="pkeiles"]but I did locate a couple that should hopefully be enough to get me started:[/quote]

After looking at these two I believe they should give a lot of help to getting started! They seem quite detailed in resources regarding the topic. The peripheral_uart_high_mtu.zip added to 283808 looks like a data extended variation of the normal peripheral_uart, so unless you've already done so I believe this and the throughput sample should be what you're looking for!

As a supplement to Case ID: 282428, I can add that topic 7 and 8 from this NCS course is a great, more detailed introduction to threads and work queues to Simons "Try using work queues" if you're new to the topic or need some refreshing.

I hope this helps you, and let me know if you have more questions!

Kind regards,
Andreas

RE: BLE Data Length Extension Usage and Example

Pamela Keiles — Wed, 27 Apr 2022 17:34:23 GMT

Hi Andreas,

I can't find the exact case that I referenced before, but I did locate a couple that should hopefully be enough to get me started:

Case ID: 283808
Case ID: 282428

It is confusing exactly how many of the config definitions need to be updated for using the extended data packet length. It would be nice if they were all connected, or there was at least a list to reference to use this stack feature. By the way I am using the latest of the nRF Connect SDK (v1.9.1) and Visual Code tools.

Regards,

Pam

RE: BLE Data Length Extension Usage and Example

AHaug — Tue, 26 Apr 2022 14:32:58 GMT

Hi Pam,

[quote user=""] In looking through the developer zone I found reference to someone using extended data length packets[/quote]

Could you supply a link to this ticket and I'll take a look on the details there for comparison? Also, which version of NCS (if you're using NCS) are you using?

[quote user=""]I was wondering if a specific example exists that uses the extended data packet feature? [/quote]

I believe the ble/throughput-sample should allow you to get started on a BLE sample that uses data extension!

1) It could be that all the CONFIGS in the sample you mention is more than what is required or that the throughput-sample contains less than what you need, so I suggest you compare them up against each other.

2) I will look closer into this tomorrow and come back with a reply then.

Let me know if this is enough to get you started and feel free to follow up with more questions!

Kind regards,
Andreas