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

regression: esp_hal::init() resets interrupts #2386

Closed
kaspar030 opened this issue Oct 22, 2024 · 1 comment · Fixed by #2377
Closed

regression: esp_hal::init() resets interrupts #2386

kaspar030 opened this issue Oct 22, 2024 · 1 comment · Fixed by #2377
Labels
bug Something isn't working
Milestone

Comments

@kaspar030
Copy link
Contributor

kaspar030 commented Oct 22, 2024

Bug description

Since #2091, esp_hal::init() unconditionally disables all interrupts.

This broke our threading, as we set up the interrupt handler before, start threading, and then in a thread call esp_hal::init(). With #2091, this now disabled our scheduler interrupt again.

Resetting all interrupts might be actually acceptable behavior (probably most users call esp_hal::init() very early), but the PR#2091 decription only mentions an API rename, and the new behavior wasn't mentioned in the changelog.

(I'm slightly grumpy because we had to track this down but of course please don't read any blame. 😉).

To Reproduce

  1. ...
  2. ...

Expected behavior

Environment

  • Target device: any xtensa
  • Crate name and version: esp-hal 0.21.1
@bugadani
Copy link
Contributor

Thanks, this will be fixed by #2377

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

3 participants