Skip to content

firmware flash: take the chip from the image when no board is given - #74

Merged
bdbarnett merged 1 commit into
mainfrom
fix/flash-offset-from-image
Oct 6, 2026
Merged

bdbarnett merged 1 commit into
mainfrom
fix/flash-offset-from-image

Conversation

@bdbarnett

Copy link
Copy Markdown
Collaborator

mpftp firmware flash --port esp32 --artifact <P4 firmware.bin> with no --board or --family wrote the image at 0x0. A P4's bootloader belongs at 0x2000, so the DEV-KIT went into a reset loop. Windows dinged on every re-enumeration until it was reflashed with --offset 0x2000.

A combined firmware.bin starts with the bootloader's image header, which carries the chip ID at byte 12. When neither a board nor a family is given, flash_esp32 now reads the family from there, so the offset comes out right for every chip in the table. --offset, --family and --board still win.

The new test plants the P4 image with no board. It passes here and fails against the old flash_esp32. The rest of test_app_image_offset.py still passes.

@bdbarnett
bdbarnett merged commit 8a12440 into main Oct 6, 2026
3 checks passed
@bdbarnett
bdbarnett deleted the fix/flash-offset-from-image branch October 6, 2026 01:13
bdbarnett added a commit that referenced this pull request Oct 6, 2026
…heading

All ten version declarations now say 0.0.12 and check_versions.py passes.
The bot's commit line becomes a written v0.0.12 entry for #74.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant