357078504d
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.
7 lines
331 B
Plaintext
7 lines
331 B
Plaintext
# 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
|