LE 2M PHY of perpherial device CYW20719

Tip / Sign in to post questions, reply, level up, and achieve exciting badges. Know more

cross mob
JiZh_4619191
Level 4
Level 4
25 replies posted 25 sign-ins 10 replies posted

Hi,

I found an API( wiced_bt_dev_status_t wiced_bt_ble_set_phy ( wiced_bt_ble_phy_preferences_t ∗ phy_preferences ) ) to configure the LE link to 1M or 2M.

And "wiced_bt_ble_phy_preferences_t" has a data field "remote_bd_addr". The "API Reference Guide" said "remote_bd_addr" is "Peer Device address".

Does this means "wiced_bt_ble_set_phy()" will set central device LE link?

If CYW20719 serve as perpherial device, how to set LE link of CYW20719?

Best regards.

0 Likes
1 Solution
Charles_Lai
Moderator
Moderator
Moderator
500 replies posted 250 solutions authored 250 sign-ins

Hi,

wiced_bt_ble_set_phy() only starts negotiation between the host and the peer device. The "remote_bd_addr" field is used to specify the link you are going to configure. Each of the device (Central / Peripheral) can call this function to explicitly change PHY between them.

And 1M / 2M PHY is something related to the link configuration which is maintained and held between the two devices, so we can't "set central / peripheral device LE link" on the specific one. The most related function to this is wiced_bt_ble_set_default_phy(), which is used for "host to configure default transmitter phy and receiver phy to be used for all subsequent connections over the LE transport."

Therefore, please note that, you can  only set default PHY on a specific device beforehand or negotiate the preferred PHY between the two peers in current connection.

There are three functions related to 2M PHY:

  • wiced_bt_dev_status_t wiced_bt_ble_set_default_phy ( wiced_bt_ble_phy_preferences_t * phy_preferences )
  • wiced_bt_dev_status_t wiced_bt_ble_set_phy ( wiced_bt_ble_phy_preferences_t * phy_preferences )
  • wiced_bt_dev_status_t wiced_bt_ble_read_phy ( wiced_bt_device_address_t remote_bd_addr, wiced_bt_ble_read_phy_complete_callback_t * p_read_phy_complete_callback )

They are used together to provide the whole control of PHY. They together will help you get the hang of PHY.

Please refer to the link below, to get detailed information:

LE 2M PHY — BLE5-Stack User's Guide 1.00.00 documentation

<<<<<<<<<<<<<>>>>>>>>>>>>>

Sincere regards from​ C. L.

<<<<<<<<<<<<<>>>>>>>>>>>>>

View solution in original post

0 Likes
1 Reply
Charles_Lai
Moderator
Moderator
Moderator
500 replies posted 250 solutions authored 250 sign-ins

Hi,

wiced_bt_ble_set_phy() only starts negotiation between the host and the peer device. The "remote_bd_addr" field is used to specify the link you are going to configure. Each of the device (Central / Peripheral) can call this function to explicitly change PHY between them.

And 1M / 2M PHY is something related to the link configuration which is maintained and held between the two devices, so we can't "set central / peripheral device LE link" on the specific one. The most related function to this is wiced_bt_ble_set_default_phy(), which is used for "host to configure default transmitter phy and receiver phy to be used for all subsequent connections over the LE transport."

Therefore, please note that, you can  only set default PHY on a specific device beforehand or negotiate the preferred PHY between the two peers in current connection.

There are three functions related to 2M PHY:

  • wiced_bt_dev_status_t wiced_bt_ble_set_default_phy ( wiced_bt_ble_phy_preferences_t * phy_preferences )
  • wiced_bt_dev_status_t wiced_bt_ble_set_phy ( wiced_bt_ble_phy_preferences_t * phy_preferences )
  • wiced_bt_dev_status_t wiced_bt_ble_read_phy ( wiced_bt_device_address_t remote_bd_addr, wiced_bt_ble_read_phy_complete_callback_t * p_read_phy_complete_callback )

They are used together to provide the whole control of PHY. They together will help you get the hang of PHY.

Please refer to the link below, to get detailed information:

LE 2M PHY — BLE5-Stack User's Guide 1.00.00 documentation

<<<<<<<<<<<<<>>>>>>>>>>>>>

Sincere regards from​ C. L.

<<<<<<<<<<<<<>>>>>>>>>>>>>

0 Likes