You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is there a simple flag that I can place in the sdkconfig file to re-enable the use of both cores. I understand that I have to be careful about global variables and if both cores try to access the same one, issues are caused but it would be very useful to run simultaneous tasks on both cores at the same time.
Searching through the files I know that the I2S non blocking uses freertos to assign to a different core but I'm also not sure how this would be implemented.
Many thanks,
Thomas
The text was updated successfully, but these errors were encountered:
Is there a simple flag that I can place in the sdkconfig file to re-enable the use of both cores.
Unfortunately there is not a simple flag.
I understand that I have to be careful about global variables and if both cores try to access the same one, issues are caused but it would be very useful to run simultaneous tasks on both cores at the same time.
The issue isn't about Python-level synchronisation as the GIL takes care of that, it's about how tasks are scheduled and interrupted by ISRs.
It would be good to solve this, and #4895 (comment) (and other discussion in that thread) is still useful to understand the problem.
Hi,
I have been trying to enable the use of both cores for micropython on the ESP32-S3. I have read:
#4611
#4895
#8197
#7258
Is there a simple flag that I can place in the sdkconfig file to re-enable the use of both cores. I understand that I have to be careful about global variables and if both cores try to access the same one, issues are caused but it would be very useful to run simultaneous tasks on both cores at the same time.
Searching through the files I know that the I2S non blocking uses freertos to assign to a different core but I'm also not sure how this would be implemented.
Many thanks,
Thomas
The text was updated successfully, but these errors were encountered: