Skip to content

[request] Which Arduino Nano Matter GPIOs are interrupt-capable? #64

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

Closed
rei-vilo opened this issue Jun 20, 2024 · 3 comments
Closed

[request] Which Arduino Nano Matter GPIOs are interrupt-capable? #64

rei-vilo opened this issue Jun 20, 2024 · 3 comments
Labels

Comments

@rei-vilo
Copy link

Summary

Which Arduino Nano Matter GPIOs are interrupt-capable?

The https://docs.arduino.cc/resources/pinouts/ABX00112-full-pinout.pdf does not provide this information.

Thank you!

@rei-vilo rei-vilo added the featurerequest Feature request label Jun 20, 2024
@rei-vilo
Copy link
Author

rei-vilo commented Jun 26, 2024

Trying again raised this error.

FREERTOS ASSERT ( !( ( xTaskGetSchedulerState() == taskSCHEDULER_SUSPENDED ) && ( xTicksToWait != 0 ) ) )

Both the SP and I²C bus are used. I tried with multiple GPIOs, both analog like A0 and digital like D1, to no avail.

@silabs-bozont
Copy link
Collaborator

Hello @rei-vilo,
All GPIO pins are interrupt capable - you can register callbacks to them.
The assertion you posted is resulting from calling an OS function (likely delay) from the callback function. Be careful - the callbacks are invoked from an interrupt context. If you post your sketch I can help you hunt down the issue which causes the assertion.

@rei-vilo
Copy link
Author

rei-vilo commented May 6, 2025

Thank you for the update. Unfortunately, I no longer have the project at hand to perform a new test.

@rei-vilo rei-vilo closed this as completed May 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants