This blog describes how you can setup a Segger Embedded Studio example for PCA10040E (emulating nRF52810) from nRF5 SDK 14.2 to use S132 v5.1.0, instead of S112. The procedure should be similar for the other toolchains.
nRF5 SDK 14.2 officially supports S132 v5.0.0, but since it is drop-in compatible, you can use S132 v5.1.0 instead of S132 v5.0.0 for nRF5 SDK 14.2. Simply flash s132_nrf52_5.1.0_softdevice.hex instead of s132_nrf52_5.0.0_softdevice.hex. s132_nrf52_5.1.0_softdevice.hex can be downloaded here.
The ble_app_uart_pca10040e_s112 example will be used as a starting point. This is chosen because it is one of the smaller Bluetooth Low Energy examples, the larger ones may not fit in the nRF52810 flash.
If you get into trouble, please post a question in the Q&A section and link to this blog.
For more information on developing on nRF52810, see this.
The compatibility matrix is updated.
The compatibility matrix also needs to be updated. Still, the community seems unaware of this update.
Also, limitations in terms of concurrent roles will be helpful.
What are the number of connections that can be handled using S132 on nRF52810?
There have been a lot of previous posts stating that S132 does not support nRF52810; eg, see: https://devzone.nordicsemi.com/f/nordic-q-a/38836/does-nrf52810-supports-concurrent-central-peripheral-role/150119#150119
Please update those posts with this new status!