djsundog/circuitpython
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
80df377e95
circuitpython/ports/esp32/boards/sdkconfig.ble

15 lines
360 B
Plaintext
Raw Normal View History

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.
CONFIG_BT_NIMBLE_PINNED_TO_CORE_0=n
CONFIG_BT_NIMBLE_PINNED_TO_CORE_1=y
CONFIG_BT_NIMBLE_PINNED_TO_CORE=1
Reference in New Issue Copy Permalink