Skip to content
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

Fixes https://github.com/vroland/epdiy/issues/196 #197

Merged
merged 1 commit into from
Jul 18, 2022

Conversation

martinberlin
Copy link
Collaborator

Fixes #196 avoiding to do:

rtc_gpio_isolate(GPIO_NUM_5);

in the V2 / Lilygo hardware that uses 5 as I2S Clock. On the other models that use number 15 this does not seem to trigger.

@jdoubleu
Copy link
Contributor

I think these changes in 6e9d620 from the #180 PR are somewhat related to this one.

@martinberlin
Copy link
Collaborator Author

It can be related, but this one specifically triggers on IO5, when using:

rtc_gpio_isolate(GPIO_NUM_5);

This is not triggering on IO 15 that is used by V6. And I really don't know what is going on with that specific pin on Lilygo model. But still not sure if my fix is appropriate so maybe we wait till the #180 PR is merged before doing this.
In older versions of this component or even the LilyGO version this didn't happen since there was no i2s_gpio_detach() this was created afterwords (I think)

@martinberlin martinberlin merged commit 3e2c515 into vroland:master Jul 18, 2022
@lanistor
Copy link

rtc_gpio_isolate(GPIO_NUM_12) this makes our buzzer not sound, because the same pin is used, is this sentence necessary?

@martinberlin martinberlin deleted the vroland-master branch November 14, 2023 16:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

RTCIO error: rtc_gpio_isolate: RTCIO number error
3 participants