Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Adding GPIO Expander(23017) Support to the library #784

Closed
Frenzyritz13 opened this issue Aug 16, 2021 · 4 comments · May be fixed by #787
Closed

Adding GPIO Expander(23017) Support to the library #784

Frenzyritz13 opened this issue Aug 16, 2021 · 4 comments · May be fixed by #787

Comments

@Frenzyritz13
Copy link

@Frenzyritz13 I just modified my post (found/fixed an error in the logic). Please be sure to use the updated snippet about _ini_pins()

This looks good Brendan! Will test it and get back to you. Also, I am going to be using 2 I2Cs and an Expander based interrupt, I am expecting some issues there as well, will keep this thread updated.

This deserves a separate thread/issue because we are no longer discussing just the ESP32's SPI bus.

Originally posted by @2bndy5 in #722 (comment)

@2bndy5
Copy link
Member

2bndy5 commented Aug 16, 2021

For reference, this is the suggested idea here: #722 (comment)

@2bndy5
Copy link
Member

2bndy5 commented Aug 16, 2021

Also, I am going to be using 2 I2Cs and an Expander based interrupt, I am expecting some issues there

I should probably mention that using any RF24::write*() call in an ISR callback is prohibited by the RF24 library because it uses millis() to detect timeouts and delayMicroseconds() for every SPI transaction on boards that have a high speed CPU. You can have a look at the interrupt_configure.ino example to see a working hint about using a volatile boolean to get around that.

@2bndy5 2bndy5 linked a pull request Sep 9, 2021 that will close this issue
@2bndy5
Copy link
Member

2bndy5 commented Oct 17, 2021

@Frenzyritz13 any updates?

@2bndy5
Copy link
Member

2bndy5 commented Jan 17, 2023

I'm closing this due to lack of activity. The associated PR (#787) will remain open for anyone that is curious, but we have no plans to support this feature.

@2bndy5 2bndy5 closed this as not planned Won't fix, can't repro, duplicate, stale Jan 17, 2023
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants