BLE scanning with nrf52810 and s112

[mst]

I'm currently porting my code from nrf52832/S132 to nrf52810/S112 (SDK14.2).

It seems that the s112 has no support for scanning, i.e., BLE_GAP_EVT_ADV_REPORT, sd_ble_gap_scan_start(), sd_ble_gap_scan_stop(), are not available any more.

I was unable to find more information on why and how this has been changed. Can anyone point me to documentation on this? And is there an easy way to achieve the same kind of scanning with the s112?

[MartinBL]

Hi,

EDIT 13.09.2018: S132 v5.1.0 is now tested, qualified, and ready to be used in production on the nRF52810. This solution includes central and observer roles. Please refer to this blog for mor info: The S132 v5.1.0 is now production tested on nRF52810

The GAP central and observer roles were removed from the S112 in version 5.1.0 to save flash space. This is briefly mentioned in the Release Notes for the S112 v5.1.0. If you have to do scanning then unfortunately you will have to use S132 which is currently not compatible with nRF52810.

[mst]

Thanks for the clarification. I feel like I'm the only one surprised, and slightly disappointed, about this design choice. I guess I have to contact my Sales Representative for more information on future support of, for example, the S132 for the nrf52810, or can you also comment on this?

[MartinBL]

I certainly understand your disappointment. I can't comment on roadmaps and future feature sets, but contacting your Sales Representative to express your concern is a good idea. If you don't know who your RSM is, send me a PM and I'll give you his details.

[Nicole]

Is this answer still valid? If yes, why is then S132 stated as compatible to nRF52810 in this document?: infocenter.nordicsemi.com/.../nRF52810_PB_v1.1.pdf

[MartinBL]

Unfortunately it is still valid. Our initial intention was for the two to be compatible, but this was down prioritised.

If this is something you care about, I urge you to contact your RSM as well.