-
Notifications
You must be signed in to change notification settings - Fork 67
New issue
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
Custom Boards - 2nd core can be used on rp2040 #320
Conversation
Firmware for this pull request: |
Firmware for this pull request: |
Firmware for this pull request: |
Firmware for this pull request: |
Firmware for this pull request: |
uint8_t command, stepper; | ||
int32_t param1, param2; | ||
|
||
while (1) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
while (true) would be prettier.
i think the description of this PR requires a bit more documentation on the actual scope and how to use it.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
see my comments.
Board and firmware folder for this pull request: |
Board and firmware folder for this pull request: |
Board and firmware folder for this pull request: |
Description of changes
On Picos the 2nd core is used to run the
set()
function of the community devices.With this change setting a new value to a community device will not lead to missed input events even if the
set()
function needs much more time.The
FreeRTOS
lib is used to initialize and run the 2nd core of a Pico. Data from the 1st core to the 2nd core is transferred by using the build infifo
. Once all data is received the 2nd core calls theset()
function of the community device.To activate this feature only one define within
custom.platformio.ini
is required. Once-DUSE_2ND_CORE
is set, this feature is enabled. If it is not set or even not available, the 2nd core of the pico is not used and everything is like before. So it's fully backward compatible, the 2nd core will not be used as long as the above mentioned flag is not set.Fixes #319