[XAP] First boot initialisation

[zvecr]

XAP Task Info

Original Issue Original spec document Current XAP Definitions Current XAP Generated Docs Placeholder PR

Description

Any work in this area needs to be discussed with QMK Collaborators first.

Bind eeprom reset logic so that dynamic keymap is populated.

• reset condition?
  • enabled features?
• via -> stores date to detect "significant" firmware change
• xap version?
• introduce version for dynamic keymap format?

[tzarc]

Maybe now with the introspection capabilities, we can use a CRC over the keymap and encodermap and use that instead of the date?

[zvecr]

hash at runtime would work, be it going to burn more cycles on boot. Would be a little more targeted which has both upsides and downsides.

Implemented at 28855f658adbb0b4f3803e960d5c9389ef7da332:

• variable keycode IDs depending on enabled features
  • enabled features somewhat need to be taken into account with the current keycode implementation
  • less of an issue with DD keycodes?
    • include keycode version in hash?

Maybe something like 2592402627e58a121347842d4f26b39e78adbadf at build time?

• maybe too aggressive in content it considers?
  • maybe "safer" due to unknowns of reset condition

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had activity in the last 90 days. It will be closed in the next 30 days unless it is tagged properly or other activity occurs. For maintainers: Please label with bug, in progress, on hold, discussion or to do to prevent the issue from being re-flagged.