lv_micropython/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
esp32: Implement BLE using Nimble from IDF 4.x. 2019-10-01 23:47:37 +10: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 23:40:04 +11:00
esp32: Implement BLE using Nimble from IDF 4.x. 2019-10-01 23:47:37 +10: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 23:40:04 +11: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 15:39:40 +11:00			`CONFIG_BT_NIMBLE_MAX_CONNECTIONS=4`