As I mentioned in my other question, I've been playing around with the bearer layer of the Mesh-Stack, to get a better understanding of how to get a robust basis for a multiprotocol implementation. I noticed that the current Mesh Stack (nRF SDK for Mesh v3.2.0) only supports Softdevice up to S132 v6.x. Nonetheless, I wanted to see how the timeslot implementation behaves when using S132 v7.x and indeed noticed that there seems to be an issue:
BLE GAP connection establishment often fails. When looking at BLE-Traffic with a sniffer, it looks like the CONNECT_IND PDU gets basically ignored.
Can you confirm whether there is such an Issue with S132 7.x?
I did test this with a basic application where I gutted most of the Mesh-Stack and am basically just running timeslot.c, bearer_handler.c and a few of their dependencies... During the timeslot I just "emulate" using it by basically stress testing the berare_handler with a lot of actions. This in itself looks to be rather stable and BLE connections seem to work properly when using the older Softdevice, but mostly fail when using Version 7.
Unfortunately, as of right now, I can't really provide any example in source code, because it is based on a proprietary scheduler. I could possibly post the two firmwares as HEX-files (one for each Softdevice), if that helps.
