Skip to content

Requesting too much EEPROM silently leads to corrupt settings #1536

@thehenkan

Description

@thehenkan

Describe the bug
When slices adding up to more bytes than are available in EEPROM are requested, the firmware happily allocates those slices. When writing to the OOB slices, other slices are corrupted.

To Reproduce
Steps to reproduce the behavior:

  • flash a sketch with many layers in EEPROM
  • write keyboard and LED layout with Chrysalis
  • reload Chrysalis and reconnect to keyboard
  • layout/colormap does not match what was written

Expected behavior
I expected some kind of error reporting. Perhaps the firmware should halt during setup if too much EEPROM is requested, perhaps it should set an error flag that Chrysalis can read. Something.

Environment (please complete the following information):

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions