Skip to content

Conversation

@kyrias
Copy link
Contributor

@kyrias kyrias commented Nov 8, 2025

Hey,

This is still a bit of a WIP but I'd like some input whether this overall approach and structure would be acceptable before I fill out the support for the other device types.

The actual block definitions only exist within Python classes so this
commit uses PyO3 to import the esptool.py eFuse block definitions and
generates arrays of the length and read address of each eFuse block.

We need the actual read address here rather than using the old offset
method because not all eFuse blocks are sequential.  (On ESP32 the block
0 read registers are followed by the block 0 write registers.)
This prevents Python being necessary to build the xtask binary for other
purposes.
@kyrias kyrias force-pushed the efuse-write branch 3 times, most recently from cd38d2e to 95bef98 Compare December 5, 2025 19:10
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.

1 participant