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

Allow partition table offset to be specified in espflash.toml, Cargo.toml [package.metadata.espflash.flash] or in the partition table itself #699

Closed
jnross opened this issue Oct 31, 2024 · 1 comment

Comments

@jnross
Copy link
Contributor

jnross commented Oct 31, 2024

For different devices, different partition table offsets may be used. To allow this to be more explicitly configured, I propose that we allow the partition table to be specified in the espflash.toml file, or even in the partition table itself.
Proposed espflash.toml:

[flash]
mode = "qio"
size = "8MB"
frequency = "80MHz"
partition_table_offset = 0x8000

Proposed partition_table.csv:

# ESP-IDF Partition Table
#----------------------------------------------------------------
# Name,         Type, SubType, Offset,   Size,     Flags
# bootloader                   0x0,      0xA000
partition_table                0xA000,   0x1000
otadata,        data, ota,     0xB000,   0x2000,
emul_efuse,     data, 5,       0xD000,   0x2000,
phy_init,       data, phy,     0xF000,   0x4000,
cps,            data, nvs,     0x13000,  0x8000,
nvs,            data, nvs,     0x1B000,  0x25000,
ota_0,          app,  ota_0,   0x40000,  0x3e0000,
ota_1,          app,  ota_1,   0x420000, 0x3e0000,

Proposed Cargo.toml:

[package.metadata.espflash]
partition_table = "../../partitions-dev.csv"
partition_table_offset = 0x8000
@SergioGasquez
Copy link
Member

Closed by #700

@github-project-automation github-project-automation bot moved this from Todo to Done in esp-rs Nov 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

No branches or pull requests

2 participants