[Bug] Update wiped my key maps

[ratijas]

Describe the Bug

The release notes page states that

The modules keep persistent settings. Firmware updates do not erase them.

However, upon updating keyboard+macropad, my key maps were erased. Yes, I updated BIOS to 4.02 afterwards (per this page), it didn't revert the missing configs.

Keyboard Used

ANSI RGB keyboard, RGB macropad

Link to product page (if applicable)

No response

Operating System

Windows 11

qmk doctor Output

Is AutoHotKey / Karabiner installed

• AutoHotKey (Windows)
• Karabiner (macOS)

Other keyboard-related software installed

No response

Additional Context

No response

[CDRXavier]

Might be due to different sketch size and inclusion of a lot of additional features, like lid close behavior.
Different versions might not have consistent emulated EEPROM locations, I recommend just having a config file ready for quick import/export.

I also don't recommend Via. Its feature set limited, and when you update firmware you have to erase the entire flash first.

[ratijas]

I have no clue what you just said, sorry. I used the official configurator at https://keyboard.frame.work/ and updated the firmware through the official updater from the support page linked in the original post.

If that was not the right way to do it, then what is?

[CDRXavier]

I have no clue what you just said, sorry.

Version 0.3.2 added some features 0.2.9 lack. This might have changed size of firmware binary, leading to a loss of settings.

This seems to be "expected behavior", since the RP2040 chip does not have a dedicated "EEPROM" that store settings. Instead, the storage is emulated on top of PROMEM, where you flash the firmware.

Furthermore, if you uploaded erase_flash.uf2, all of PROGMEM will be erased, including saved settings.

If that was not the right way to do it, then what is?

Personally I use QMK command line and config settings. These by themselves is not too crazay, but the process of setting up a environment to compile said firmware is. However, when you are compiling your own firmware(s), you get direct control. This eliminates any potential screw-ups caused by confusion, and you retain your settings/profile (as per the config files). You also get to do a few things you can't do with Via, like changing behavior with numlock status, etc.

[ratijas]

The guide page stated clearly:

The modules keep persistent settings. Firmware updates do not erase them.

Sorry, I don't understand how such technicalities as "firmware binary size" or whatever suddenly turn loss of settings into an expected behavior.

Furthermore, if you uploaded erase_flash.uf2, all of PROGMEM will be erased, including saved settings.

I have no idea, I just double-clicked the officially provided exe.

I'm sorry to sound like a dumb user, but these technical arguments sound more like poor excuses that anything, really. We can't just update the laptop/keyboard without screwing it over?

[CDRXavier]

poor excuses

They should've documented better. From a user perspective, they should just provide 1 set of tools to modify firmware somewhat easily. In reality, there's likely quirks to each of the two (three?) ways.

I don't know how the update exe works. Or fwupdmgr.

turn loss of settings into an expected behavior.

I guess its expected as per code-side. Though, going through the list of 50 commits between 0.2.9 and 0.3.2, I cant seem to be able to find anything ...