mirror of
https://github.com/micropython/micropython.git
synced 2026-01-06 20:20:14 +01:00
esp32: Pin MicroPython to core 1 again.
This follows up on #5489, where we changed the esp32 core pinning to core 0 in order to work around an issue with IDF < 4.2.0. Now that IDF > 4.2.0 is available, we allow pinning back to core 1, which eliminates some problematic callback latency with WiFi enabled. NimBLE is also pinned to core 1 - the same core as MicroPython - when using IDF >=4.2.
This commit is contained in:
@@ -7,11 +7,3 @@ 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
|
||||
|
||||
6
ports/esp32/boards/sdkconfig.nimble_core0
Normal file
6
ports/esp32/boards/sdkconfig.nimble_core0
Normal file
@@ -0,0 +1,6 @@
|
||||
# For 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
|
||||
6
ports/esp32/boards/sdkconfig.nimble_core1
Normal file
6
ports/esp32/boards/sdkconfig.nimble_core1
Normal file
@@ -0,0 +1,6 @@
|
||||
# For IDF >=4.2, we are able to put NimBLE on core 1, and for synchronisation
|
||||
# with the ringbuffer and scheduler MP needs to be on the same core.
|
||||
# MP on core 1 prevents interference with WiFi for time sensitive operations.
|
||||
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
Block a user