circuitpython/ports/esp32/boards/sdkconfig.ble

# Note this requires building with IDF 4.x
CONFIG_BT_ENABLED=y
CONFIG_BTDM_CTRL_MODE_BLE_ONLY=y
CONFIG_BTDM_CTRL_MODE_BR_EDR_ONLY=
CONFIG_BTDM_CTRL_MODE_BTDM=

CONFIG_BT_NIMBLE_ENABLED=y

CONFIG_BT_NIMBLE_MAX_CONNECTIONS=4

# Pin to the same core as MP.
# Until we move to IDF 4.2+, we need NimBLE on core 0, and for synchronisation
# with the ringbuffer and scheduler MP needs to be on the same core.
# See https://github.com/micropython/micropython/issues/5489
CONFIG_BT_NIMBLE_PINNED_TO_CORE_0=y
CONFIG_BT_NIMBLE_PINNED_TO_CORE_1=n
CONFIG_BT_NIMBLE_PINNED_TO_CORE=0
esp32: Implement BLE using Nimble from IDF 4.x. 2019-10-01 09:47:37 -04:00			`# Note this requires building with IDF 4.x`
			`CONFIG_BT_ENABLED=y`
			`CONFIG_BTDM_CTRL_MODE_BLE_ONLY=y`
			`CONFIG_BTDM_CTRL_MODE_BR_EDR_ONLY=`
			`CONFIG_BTDM_CTRL_MODE_BTDM=`
esp32: Run NimBLE on the app core. This prevents issues with concurrent access to the ringbuf. MICROPY_BEGIN_ATOMIC_SECTION is only atomic to the same core. We could address this with a mutex, but it's also not safe to call mp_sched_schedule across cores. 2019-10-14 08:40:04 -04:00
esp32: Implement BLE using Nimble from IDF 4.x. 2019-10-01 09:47:37 -04:00			`CONFIG_BT_NIMBLE_ENABLED=y`
esp32: Run NimBLE on the app core. This prevents issues with concurrent access to the ringbuf. MICROPY_BEGIN_ATOMIC_SECTION is only atomic to the same core. We could address this with a mutex, but it's also not safe to call mp_sched_schedule across cores. 2019-10-14 08:40:04 -04:00
extmod/modbluetooth: Increase maximum connections from 1 to 4. This avoids a confusing ENOMEM raised from gap_advertise if there is currently an active connection. This refers to the static connection buffer pre-allocated by Nimble (nothing to do with MicroPython heap memory). 2019-10-14 00:39:40 -04:00			`CONFIG_BT_NIMBLE_MAX_CONNECTIONS=4`
esp32: Run NimBLE on the app core. This prevents issues with concurrent access to the ringbuf. MICROPY_BEGIN_ATOMIC_SECTION is only atomic to the same core. We could address this with a mutex, but it's also not safe to call mp_sched_schedule across cores. 2019-10-14 08:40:04 -04:00
			`# Pin to the same core as MP.`
esp32: Pin MicroPython and NimBLE tasks to core 0. MicroPython and NimBLE must be on the same core, for synchronisation of the BLE ringbuf and the MicroPython scheduler. However, in the current IDF versions (3.3 and 4.0) there are issues (see e.g. #5489) with running NimBLE on core 1. This change - pinning both tasks to core 0 - makes it possible to reliably run the BLE multitests on esp32 boards. 2020-08-18 20:46:09 -04:00			`# Until we move to IDF 4.2+, we need NimBLE on core 0, and for synchronisation`
			`# with the ringbuffer and scheduler MP needs to be on the same core.`
			`# See https://github.com/micropython/micropython/issues/5489`
			`CONFIG_BT_NIMBLE_PINNED_TO_CORE_0=y`
			`CONFIG_BT_NIMBLE_PINNED_TO_CORE_1=n`
			`CONFIG_BT_NIMBLE_PINNED_TO_CORE=0`