Skip to content

Improve reading efuses #829

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
wants to merge 2 commits into from
Closed

Conversation

SergioGasquez
Copy link
Member

@SergioGasquez SergioGasquez commented Apr 4, 2025

Trying to improve the way we handle eFuses, any input is welcome

No public changes, so skip-changelog

@SergioGasquez SergioGasquez requested review from jessebraham and playfulFence and removed request for jessebraham April 4, 2025 10:32
@SergioGasquez SergioGasquez added the skip-changelog Skips the changelog CI check label Apr 7, 2025
@SergioGasquez SergioGasquez marked this pull request as ready for review April 7, 2025 13:16
@MabezDev
Copy link
Member

MabezDev commented Apr 7, 2025

Can we leverage the CSV files that we use in esp-hal for efuse access here? I'd really like to avoid the manual impls if possible, because it will be a chore for new chip bring up.

For example, all chips appear to have a "MAC": https://docs.espressif.com/projects/rust/esp-hal/1.0.0-beta.0/esp32/esp_hal/efuse/constant.MAC.html constant in the CSV's so we can leverage that to only have to process this field in one way.

@jessebraham
Copy link
Member

As we've discussed privately, I've been working on an alternate approach for this. While not quite complete yet, I'm far enough along to be confident that it will work. So, thanks for the PR, but will close this in favour of my upcoming PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
skip-changelog Skips the changelog CI check
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Current API for reading eFuse values is confusing/difficult to use
3 participants