Skip to content

fix: embed full ship version in .file_name region - #90

Open
AlexKlimaj wants to merge 1 commit into
ark-releasefrom
fix/embed-ship-version-in-file-name
Open

fix: embed full ship version in .file_name region#90
AlexKlimaj wants to merge 1 commit into
ark-releasefrom
fix/embed-ship-version-in-file-name

Conversation

@AlexKlimaj

Copy link
Copy Markdown
Member

Summary

ARK ship releases use VERSION_PATCH in artifact names (3.0.2-ark), but EEPROM only stores major/minor (3.0) for AM32 protocol compatibility. The configurator therefore always showed 3.0 after flash.

Change

Embed the full ship string as a second C-string in the 32-byte .file_name region:

ARK_4IN1_F051\03.0.2-ark\0…
  • Asset matching still uses only FILE_NAME (decode up to first NUL).
  • Configurator (companion PR) reads the second string for display.
  • No EEPROM layout change.

Companion

ark32-configurator: show patch version + match 3.0.x assets

Test plan

  • Build ARK_4IN1_F051; strings / hex dump of .file_name shows board name + 3.0.2-ark
  • Size / codegen checks still pass (.file_name non-empty)
  • With updated configurator, connect after flash shows 3.0.2-ark

EEPROM still stores only major/minor (3.0) for protocol compatibility.
The configurator could not show ARK patch releases (3.0.1, 3.0.2) after
flash because those fields never include VERSION_PATCH.

Embed `MAJOR.MINOR.PATCH[-TAG]` as a second C-string after FILE_NAME in
the 32-byte .file_name flash region so tools that already read that area
can display the full ship version (e.g. 3.0.2-ark) without changing the
EEPROM layout. Older tools still only decode up to the first NUL.
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