We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Board support
M5Stack ATOM
When using an M5Stack-ATOM and nimble library, using defaults board parameters ends up to SW reset:
assert failed: interrupt_hlevel_disable bt.c:517 (xPortGetCoreID() == CONFIG_BTDM_CTRL_PINNED_TO_CORE)
This could be avoided by letting the Events and the Arduino loop to run on core0
make following options available in the Tools menu for board M5stack-ATOM.
Tools
This is achievable by adding these lines at the relevant place in boards.txt: `
m5stack-atom.menu.LoopCore.1=Core 1 m5stack-atom.menu.LoopCore.1.build.loop_core=-DARDUINO_RUNNING_CORE=1 m5stack-atom.menu.LoopCore.0=Core 0 m5stack-atom.menu.LoopCore.0.build.loop_core=-DARDUINO_RUNNING_CORE=0
m5stack-atom.menu.EventsCore.1=Core 1 m5stack-atom.menu.EventsCore.1.build.event_core=-DARDUINO_EVENT_RUNNING_CORE=1 m5stack-atom.menu.EventsCore.0=Core 0 m5stack-atom.menu.EventsCore.0.build.event_core=-DARDUINO_EVENT_RUNNING_CORE=0 `
Configuring the nimble library is more cumbersome for the end-user. (and does not work)
No response
The text was updated successfully, but these errors were encountered:
feature(m5stack-atom): allow events and loop on core0
dae7562
Closes espressif#8461
feature(m5stack-atom): allow events and loop on core0 (#8462)
e2c4799
Closes #8461 Co-authored-by: Gautier Seidel <[email protected]> Co-authored-by: Jan Procházka <[email protected]>
Successfully merging a pull request may close this issue.
Related area
Board support
Hardware specification
M5Stack ATOM
Is your feature request related to a problem?
When using an M5Stack-ATOM and nimble library, using defaults board parameters ends up to SW reset:
assert failed: interrupt_hlevel_disable bt.c:517 (xPortGetCoreID() == CONFIG_BTDM_CTRL_PINNED_TO_CORE)
This could be avoided by letting the Events and the Arduino loop to run on core0
Describe the solution you'd like
make following options available in the
Tools
menu for board M5stack-ATOM.This is achievable by adding these lines at the relevant place in boards.txt:
`
m5stack-atom.menu.LoopCore.1=Core 1
m5stack-atom.menu.LoopCore.1.build.loop_core=-DARDUINO_RUNNING_CORE=1
m5stack-atom.menu.LoopCore.0=Core 0
m5stack-atom.menu.LoopCore.0.build.loop_core=-DARDUINO_RUNNING_CORE=0
m5stack-atom.menu.EventsCore.1=Core 1
m5stack-atom.menu.EventsCore.1.build.event_core=-DARDUINO_EVENT_RUNNING_CORE=1
m5stack-atom.menu.EventsCore.0=Core 0
m5stack-atom.menu.EventsCore.0.build.event_core=-DARDUINO_EVENT_RUNNING_CORE=0
`
Describe alternatives you've considered
Configuring the nimble library is more cumbersome for the end-user. (and does not work)
Additional context
No response
I have checked existing list of Feature requests and the Contribution Guide
The text was updated successfully, but these errors were encountered: