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.

Sign up for GitHub

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

Jump to bottom

ESP32: RTC domain must be initialized on boot #2105

Open
MabezDev opened this issue Sep 6, 2024 · 0 comments
Open

ESP32: RTC domain must be initialized on boot #2105

MabezDev opened this issue Sep 6, 2024 · 0 comments
Labels
1.0 non-breaking Not needed for 1.0 and can be supported without breaking the driver. chip:esp32 Issue related to ESP32 chip

Comments

@MabezDev
Copy link
Member

MabezDev commented Sep 6, 2024

I didn't label this as a bug yet, but if crate::rtc_cntl::Rtc::new(&mut peripherals.LPWR); is not called on boot on the esp32, many things get broken, namely wifi. Given that we always do this, it's not a problem yet but if we ever resolve #1698 it will be.

context: #2104
@MabezDev MabezDev added the chip:esp32 Issue related to ESP32 chip label Sep 6, 2024
@github-project-automation github-project-automation bot moved this to Todo in esp-rs Sep 6, 2024
@MabezDev MabezDev mentioned this issue Sep 16, 2024
Closed
@bugadani bugadani mentioned this issue Dec 13, 2024
Open
@tom-borcin tom-borcin added 1.0 non-breaking Not needed for 1.0 and can be supported without breaking the driver. and removed 1.0-blocker labels Dec 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
1.0 non-breaking Not needed for 1.0 and can be supported without breaking the driver. chip:esp32 Issue related to ESP32 chip
Projects
esp-rs
Status: Todo
Milestone
No milestone
Development

No branches or pull requests
2 participants
@MabezDev @tom-borcin