Alternating between Central + Peripheral and Peripheral + Peripheral in a memory constrained environment

RE: Alternating between Central + Peripheral and Peripheral + Peripheral in a memory constrained environment

Hieu — Mon, 13 May 2024 09:15:46 GMT

As the device has the control in exposing what capability it has, you can simply implement some logic to let it advertise and not scan when it is to serve as P2, or let it scan and not advertise when it is to serve as C.

You can also reconfigure the SoftDevice with sd_ble_cfg_set(). However, because you are using so few connections, that isn't required. It also doesn't bring any benefit in your use case. Furthermore, its usage is wrapped in the SoftDevice handler library, so you need to understand how it is used there and make sure there is no conflicts. Overall, just very little benefit, so I don't recommend this approach.

RE: Alternating between Central + Peripheral and Peripheral + Peripheral in a memory constrained environment

Kelso — Fri, 10 May 2024 21:45:28 GMT

While I see that is possible (and I note that it uses less memory), it's not clear to me how I'm supposed to manage the connections so only one of P2 or C are active, particularly while P1 is in use.

RE: Alternating between Central + Peripheral and Peripheral + Peripheral in a memory constrained environment

Hieu — Fri, 10 May 2024 21:29:37 GMT

Hello Kelso,

It seems possible to reduce NRF_SDH_BLE_TOTAL_LINK_COUNT to 2, while still keeping the Peripheral Link Count at 2.
However, please let me double check with someone more familiar with the topic before giving you the final conclusion.

Hieu