How many CENTRAL_LINK_COUNT and PERIPHERAL_LINK_COUNT allowed in CHECK_RAM_START_ADDRESS()?

RE: How many CENTRAL_LINK_COUNT and PERIPHERAL_LINK_COUNT allowed in CHECK_RAM_START_ADDRESS()?

Petter Myhre — Mon, 29 Jan 2018 11:36:35 GMT

No problem. If I answered your question I would appreciate if you could accept my answer by clicking the grey circle next to it.

RE: How many CENTRAL_LINK_COUNT and PERIPHERAL_LINK_COUNT allowed in CHECK_RAM_START_ADDRESS()?

Nobuaki — Fri, 26 Jan 2018 00:55:46 GMT

Hi Peter, Thank you for your information. We will consult this information with our client. Thanks,

RE: How many CENTRAL_LINK_COUNT and PERIPHERAL_LINK_COUNT allowed in CHECK_RAM_START_ADDRESS()?

Petter Myhre — Thu, 25 Jan 2018 09:45:18 GMT

CENTRAL_LINK_COUNT=8 + PERIPHERAL_LINK_COUNT =1 is not supported by S132 v2.0.1.

If you want this you need to switch to S132 v4.x or later. I recommend using S132 v5.0.x with SDK 14.2.0.

With it you can have:

Concurrent central, observer, peripheral, and broadcaster roles with up to twenty concurrent connections along with one Observer and one Broadcaster

RE: How many CENTRAL_LINK_COUNT and PERIPHERAL_LINK_COUNT allowed in CHECK_RAM_START_ADDRESS()?

Nobuaki — Thu, 25 Jan 2018 05:35:17 GMT

Addtional questions.

Could you clarify the reason more if "8 central links and 1 peripheral link setup fails, is most likely because the maximum number of concurrent connections is 8" is true, the reason is derived from BLE Core Spec or acutual performace that IC can support for concurret sessions ?