Other Parts Discussed in Thread: CC2642R
Hello,
Our goal here is to allow either 1M or Coded but not 2M.
On init and before connection was established we call
HCI_LE_SetDefaultPhyCmd(HCI_PHY_USE_PHY_PARAM, HCI_PHY_1_MBPS|HCI_PHY_CODED, HCI_PHY_1_MBPS|HCI_PHY_CODED);
However, after connection was established, iPhone SE is requesting to change the PHY to 2M and the request is accepted (without having any such request in the app). I am able to see this on the Ellisys Bluetooth capture.
First thing to note, both the doc and the source code are of rather low quality I would say. It seems from the link bellow, that `allPhys` can be HCI_PHY_USE_PHY_PARAM or HCI_PHY_USE_ANY_PHY. There is no detailed and clear explanation on those anywhere.
In fact, looking at
Whoever wrote that article may have made a mistake too? Shouldn't this be HCI_PHY_USE_PHY_PARAM if we wanted the given params to be used?
I'm just guessing based on the next example if we consider the API to be consistent.
we use multi role, and I see the following
Does this mean that, if we don't want our call to `HCI_LE_SetPhyCmd
` for a connected device, to impact and change change the default PHY for a potentially connecting other device in the future, we we need to call HCI_LE_SetDefaultPhyCmd
every time after HCI_LE_SetPhyCmd
in order to "revert" the default PHY for subsequent connections?
Thank you,
Jerome