-
Notifications
You must be signed in to change notification settings - Fork 7.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Nimble: Added Walkthrough tutorial for phy_prph example. (IDFGH-9693) #11034
Nimble: Added Walkthrough tutorial for phy_prph example. (IDFGH-9693) #11034
Conversation
|
||
## Introduction | ||
|
||
In this tutorial, the ble_phy peripheral example code for the espressif chipsets with BLE5.0 support is reviewed. This example aims at understanding how to establish connections on preferred PHY and changing LE PHY once the connection is established. The code implements a BLE Peripheral PHY, which establishes a connection on LE 1M PHY and switches to LE 2M PHY/CODED once the connection is established. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"This example aims at understanding how to establish connections on preferred PHY and changing LE PHY once the connection is established"
To
"This example aims at understanding how to accept incoming connections on preferred PHY and process the request to change LE PHY once the connection is established"
|
||
``` | ||
|
||
The main function calls `ble_svc_gap_device_name_set()` to set the default device name. 'blecent_phy' is passed as the default device name to this function. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
change "blecent_phy" to "bleprph-phy"
} | ||
``` | ||
|
||
To support increased messaging, BLE5.0 is added with extended advertising PDUs. These PDUs are broadcast-only events (like electronic beacons). The following function is used to make extended advertisements. In Bluetooth® 4.0, all advertising was done on 3 of the 40 – 2.4GHz ISM band channels. With Bluetooth 5 there are now two sets of advertising channels: primary and secondary. The primary advertising channels are the original 3 of the 40 advertising channels defined in Bluetooth 4. While the secondary advertising channels use the 37 fixed channels previously reserved for data. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Bluetooth 4 --> Bluetooth 4.0
|
||
```c | ||
|
||
static void |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This section can be removed. Just keep ext_bleprph_advertise.
|
||
To support increased messaging, BLE5.0 is added with extended advertising PDUs. These PDUs are broadcast-only events (like electronic beacons). The following function is used to make extended advertisements. In Bluetooth® 4.0, all advertising was done on 3 of the 40 – 2.4GHz ISM band channels. With Bluetooth 5 there are now two sets of advertising channels: primary and secondary. The primary advertising channels are the original 3 of the 40 advertising channels defined in Bluetooth 4. While the secondary advertising channels use the 37 fixed channels previously reserved for data. | ||
|
||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Add a line describing, that as s_current_phy value keeps changing , the advertising data also gets modified.
f014765
to
f9a895c
Compare
Thanks for your contribution. |
sha=55fd7d43c1995ff2351da51aaaa4f2df6f71de2a |
sha=f9a895c9a80a83be0e17557b77b1403b47021bd7 |
|
Thanks for contribution again, sorry for very slow turnaround, changes have been merged with 6e1d60e. |
No description provided.