ESP Flash Address Planner
Plan local ESP firmware file ranges before flashing. Check overlap, sector alignment, partition boundaries, free regions, and flash bounds.
Address is the starting location in device memory, usually written as hexadecimal (for example 0x10000). Copy it from your firmware instructions; 0x0 is not right for every file. Size accepts bytes, K or M.
Optional partition CSV
Used as a reference for boundary warnings. It is not handed to the flasher. Bootloader CSV rows need target-specific configuration and are unsupported here. Ordinary automatic offsets must be blank, not N/A.
Add local file metadata and documented addresses, then generate a plan.
The planner reads selected filenames and sizes only. It never reads firmware bytes.
Waiting for a flash layout
| File | Address | Bytes | End |
|---|
WARNINGS
FREE REGIONS
Handoff stores filename, byte size, and address in sessionStorage for one use. Firmware bytes are never stored. The flasher requires you to re-select every file and review every address before writing.
PLAN, THEN REVIEW
Place the ranges.
Keep the write explicit.
Geometry, not board advice.
The planner sorts occupied ranges, calculates free regions, and flags pairwise overlap, 4-KiB alignment, flash bounds, and files that cross an optional partition boundary. Always use addresses published for your exact firmware and board.
The handoff cannot flash.
Opening the flasher transfers one-use metadata only. It does not connect to hardware, select files, carry firmware bytes, grant consent, or start a write.