Revisit EEPROM-based Harp Register Functionality

[Poofjunior]

I think it's worth revisiting behavior that needs to persist across device reboots (nonvolatile), and whether that's something we want.

Currently the Pico Core does not implement registers with features that require behavior that assumes nonvolatile memory (referred to as EEPROM in the protocol docs). This behavior is tied some behaviors attached to certain registers in the Harp Core.

• Harp Core Registers
  • RESET_DEV
  • DEVICE_NAME

Per the protocol spec for the RESET_EE bit in RESET_DEV,

If set to 1, the device resets and reboots with all the registers, both Common and Applicatin registers, with the values saved on the non-volatile memory, usually an EEPROM. The EEPROM values will remain the permanent boot option. This bit is always read as 0.

This is actually quite difficult to implement per device, since functionality isn't strictly tied to the register location in memory by default.

(From Feb 27, 2025 meeting discussion.)