How to enable BLE 2MBPS

RE: How to enable BLE 2MBPS

vn2000 — Mon, 06 Mar 2023 08:25:20 GMT

Thanks Hieu.

Viet

RE: How to enable BLE 2MBPS

Hieu — Mon, 27 Feb 2023 06:51:59 GMT

No problem. Happy to help.

By the way, I forgot to mention it last time, but I also saw that you can use the CLI to config data length, no need to change it directly in the code.

RE: How to enable BLE 2MBPS

vn2000 — Mon, 27 Feb 2023 04:24:13 GMT

Ok thank you Hieu.

RE: How to enable BLE 2MBPS

Hieu — Fri, 24 Feb 2023 08:38:57 GMT

Hi vn2000,

In main.c/cli_init(), you can see that baud rate is not configured in the UART config. That means the sample just use UART_DEFAULT_CONFIG_BAUDRATE defined in sdk_config.h. Therefore, there are two ways: change UART_DEFAULT_CONFIG_BAUDRATE in sdk_config.h, or add UART configuration in cli_init().

In my quick tests, it appears that if you connect RTTs, the UART CLI and logging don't work very well in high baud rate (921K, 1M), so please watch out for that.

If you want to do more advance stuffs, you can research into the CLI module and change the backend to libUARTE to see if that can improve things.

RE: How to enable BLE 2MBPS

vn2000 — Fri, 24 Feb 2023 07:25:06 GMT

Hi Hieu,

I just have one question regarding the ATT_MTU example. How can I change the baud rate in the firmware?

RE: How to enable BLE 2MBPS

Hieu — Wed, 22 Feb 2023 10:51:44 GMT

Hi vn2000,

[quote user="vn2000"]I don't know why it was not set to 251 as default like the dummy board.[/quote]

They are probably different configurations for different test cases. You could see our publicize throughput numbers at the following link, where different configurations also result in different results:

https://infocenter.nordicsemi.com/topic/sds_s140/SDS/s1xx/ble_data_throughput/ble_data_throughput.html

That said, BLE devices can have different data length when they are not connected. However, once connected, they should agree on the same data length during connection parameters update. It could be that the example is setup to not allow data length update, in order to ensure the test case is fixed. You should be able to find the details in the example's code.

It's a bit odd that my test didn't encounter the same issue. Perhaps because I used the precompiled hex files directly. I hope things work well for you now.

[quote user="vn2000"]Nordic is the best.[/quote]

Thank you for the kind words.

RE: How to enable BLE 2MBPS

vn2000 — Wed, 22 Feb 2023 10:05:39 GMT

Hello Hieu,

I can make it work now. The only thing I have to set the data length to 251 on the tester. I don't know why it was not set to 251 as default like the dummy board. I can fix it in the firmware.

Anyway thank you for your help. Nordic is the best.

RE: How to enable BLE 2MBPS

Hieu — Tue, 21 Feb 2023 22:33:29 GMT

Welcome back vn2000,

The Data Length doesn't seem to have to be equal.
I reviewed the source code and see that the example would complain "Wrong board setup!" if you call run from the dummy/responder board.
Please command "run" on the tester board.

Here is my log for your reference.

RE: How to enable BLE 2MBPS

vn2000 — Mon, 20 Feb 2023 09:15:36 GMT

Hi Hieu,

I was tied up by another task last couple days. Now I compiled and downloaded both boards and I encountered some problems.

On the tester board, I pushed the button 3 and I see this:

throughput example:~$ config print
==== Current test configuration ====
Board role: tester
ATT MTU size: 247
Data length: 27
Connection interval: 6 units
Connection length ext: on
Preferred PHY: 2 Mbps
GAP event length: 400

On the dummy board, I pushed the button 4 and I see this:

throughput example:~$ config print
==== Current test configuration ====
Board role: dummy
ATT MTU size: 247
Data length: 251
Connection interval: 6 units
Connection length ext: on
Preferred PHY: 2 Mbps
GAP event length: 400

The Data length are different. Do they need to be equal?

When I type 'run', the dummy board complained:

'Wrong board setup!'

Do you have any suggestion?

RE: How to enable BLE 2MBPS

Hieu — Thu, 09 Feb 2023 09:27:03 GMT

Hi vn2000,

Yes, the path to the example and a step-by-step guide to perform the test are all include in the link in my previous answer 🙂

RE: How to enable BLE 2MBPS

vn2000 — Thu, 09 Feb 2023 07:47:04 GMT

Hi Hieu,

I want to make sure I'm using the right example you suggested. I'm using SDK V17;

\nRF5_SDK\V17\examples\ble_central_and_peripheral\experimental\ble_app_att_mtu_throughput

So I will use this same example on both central and peripheral device?

RE: How to enable BLE 2MBPS

Hieu — Wed, 08 Feb 2023 13:40:57 GMT

Hi vn2000,

An even better way to confirm whether you have 2M PHY is to get a sniffer trace. You can use the nRF Sniffer for that.

The Throughput Example is created for throughput testing purpose. Would you like to give that a try?
Here is its documentation: https://infocenter.nordicsemi.com/topic/sdk_nrf5_v17.1.0/ble_sdk_app_att_mtu.html.

Hieu

RE: How to enable BLE 2MBPS

vn2000 — Wed, 08 Feb 2023 07:33:41 GMT

Hi Hieu,

I made the following changes in BLE_GAP_EVT_PHY_UPDATE.

ble_gap_evt_t const * const p_gap = &p_ble_evt->evt.gap_evt;

case BLE_GAP_EVT_PHY_UPDATE:
printf("Received BLE_GAP_EVT_PHY_UPDATE (RX:%d, TX:%d, status:%d)",
p_gap->params.phy_update.rx_phy,
p_gap->params.phy_update.tx_phy,
p_gap->params.phy_update.status);
break;

I see the output:
Received BLE_GAP_EVT_PHY_UPDATE (RX:2, TX:2, status:0).

So it looks like the RX and TX PHY are changed to 2MBPS. But why don't I get a speed change? Could it be my test program didn't work correctly. Do you recommend any test program that tests the 2MBPS throughput?

Thanks.

RE: How to enable BLE 2MBPS

Hieu — Mon, 06 Feb 2023 13:32:45 GMT

Hi vn2000,

Could you go deeper into the event structure and get the details of BLE_GAP_EVT_PHY_UPDATE?

You can get from the fields of p_ble_evt->gap.evt.phy_update.

Reference: infocenter.nordicsemi.com/.../structble__gap__evt__phy__update__t.html

Hieu