It looks like you are using the SoftDevice Controller outside of the SDK, and that this may be an integration issue. Specifically, I suspect you have not called the correspoinding sdc_support_* function befor e initiating a control procedure. The documentation on this is a bit slim, but you can see an exmaple of this under Feature inclusing in the first message sequence chart under Integration with applications. You can see an example of how this is doen in the SDK here.
Yes, that was the problem. I did not realize there was "support_phy_update_peripheral" and "support_phy_update_central" in addition to support 2m phy. Thanks!
However, I did notice that these are missing from the message sequence chart. It just enables 2M phy, but from my understanding, you have to connect with 1M phy and set 2M phy after connection. Am I wrong?
It is possible to advertise and scan on 2M PHY using that as primary phy and thus establish the connection there, without every using 1M Phy. (Perhaps not of so much use as you are not using the SDK, but you can see samples of that with the Central Heart Rate Monitor with Coded PHY sample.
