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
Describe the bug
When writing an ISR using the Interrupt manager, it is not clear which functions are safe to use in an ISR (e.g. interrupt safe). While there is an Arduino documentation page for this (https://www.arduino.cc/reference/en/language/functions/external-interrupts/attachinterrupt/), the ability to create check flag interrupts means these standard rules are changed in certain conditions (volatile keyword?). To fix this, we should specify a list (or a general rule) of which operations are allowed to be used in an ISR for each type of ISR Loom allows.
The text was updated successfully, but these errors were encountered:
Upon discussion, it was decided that Loom would discontinue support for SAMD immediate ISRs, and only provide an API for the check flag style. This decisions was made to minimize the amount of programming proficiency required to create an ISR, and due to the lack of instances in which a true immediate ISR is needed.
Describe the bug
When writing an ISR using the Interrupt manager, it is not clear which functions are safe to use in an ISR (e.g. interrupt safe). While there is an Arduino documentation page for this (https://www.arduino.cc/reference/en/language/functions/external-interrupts/attachinterrupt/), the ability to create check flag interrupts means these standard rules are changed in certain conditions (volatile keyword?). To fix this, we should specify a list (or a general rule) of which operations are allowed to be used in an ISR for each type of ISR Loom allows.
The text was updated successfully, but these errors were encountered: