This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Advertising and Performing a Connection Over 2MPHY (2Mbps)

Hi

I would like to perform a connection over 2MPHY instead of 1MPHY; is there an example to show this? This should be doable according to the softdevice v6.1.0 changelog. I tried setting the secondary advertising channel to 2MPHY (ble_gap_adv_params->secondary_phy) and that worked fine. However, when I set the connection PHYs to 2MPHY (ble_gap_scan_params->scan_phys) I get an NRF_FAULT as follows:-

NRF_FAULT: id=ME\01  pc=0x20296  info=536935719

I then tried setting the connection PHYs to 1MPHY and the connection succeeded, however, through the sniffer I can see that the connection is being performed over 1MPHY and not 2MPHY. Please note that in both of the above cases I set the connection type to extended (ble_gap_scan_params->extended) and set the advertising type to BLE_GAP_ADV_TYPE_EXTENDED_CONNECTABLE_NONSCANNABLE_UNDIRECTED.

I am using the nRF52832 with softdevice S132 v6.1.0 and SDK 15.0.0.

Thanks

Youssif

Parents
  • Hi,

    The stack team noticed that this could be caused do to some null parameters in the arguments in connect request. 

    I believe the workaround for 6.1 is to set scan_phys = 1M | 2M

    Note: For 6.1, there is no way for the application to disallow to create a connection on 1M. The behavior may remain the same or change is a possible 6.2 or 6.1.1 (if such a SoftDevice is released).

    To disallow establishing connections on CODED: Do not use extended scanning
    To disallow establishing connections on 2M: Do not use extended scanning

  • Thanks a lot, I was able to establish a connection over 2MPHY and verified with a sniffer. However, from your sentence:- "For 6.1 there is no way for the application to disallow to create a connection on 1M" it seems that you are implying that a connection will always occur on 1MPHY?

Reply Children
Related