Massdrop Ctrl rgb setting doesn't save after computer is turned off.

more_vert
Whenever I turn my computer on from being shut off, the rgb setting always resets. It only saves the rgb setting if the computer is restarted. Would anyone know the solution to this problem? Thank you.
8
37
remove_red_eye
1.7K

search
close
ottobonn
10
Oct 3, 2020
I had the same problem and just got this working. I am using the CTRL, but I think what I did should work with the ALT as well. The keyboard comes from the factory without persistent storage (nonvolatile memory) enabled. To get the settings to stay when the keyboard loses power, we have to enable nonvolatile memory in the keyboard (using a modified version of mdloader) and also update the default keymap to save the settings in the nonvolatile memory (using a modified default QMK keymap). Enable SmartEEPROM on the keyboard First, to enable nonvolatile memory, we will use a feature called "Smart EEPROM" that comes with the ATSAMD51 chips. I have created a fork of mdloader at https://github.com/ottobonn/mdloader. You will need to check out this fork of the Massdrop loader and run the new Smart EEPROM command to update your keyboard settings to enable nonvolatile memory. Alternatively, you can download the compiled release at https://github.com/ottobonn/mdloader/releases/tag/1.1.0. The next step depends on your OS. If you're on Windows, you will use mdloader.exe, and if you're on a Mac or Linux you will use mdloader.
  • On a Mac or Linux, run the command like this: `./mdloader --first --smarteep`.
  • On Windows, run it like this: `mdloader.exe --first --smarteep`
Note that the keyboard will not reboot automatically after this command, so you should unplug it and plug it in again to start it up. For reference, the changes to the loader in this fork are from the pending PR here: https://github.com/Massdrop/mdloader/pull/16

Update your keymap to save your settings Now to update the default keymap to save the settings. I created a fork of the latest QMK today and added the required changes to it: https://github.com/ottobonn/qmk_firmware These changes include a new default keymap for the CTRL that saves a bunch of settings to the nonvolatile memory, and some changes based on community work to support SmartEEPROM in QMK, which I have adapted to make a bit more readable. Check out the master branch on this fork of QMK and `make massdrop/ctrl:default_md` to build the new keymap. I have the Drop CTRL and I have tested these steps to persist the settings even after unplugging the keyboard, and it's working great! I am planning to add support for the ALT soon as well. If you need help adapting the CTRL keymap to the ALT, let me know.
(Edited)
Devil_U_Know
80
Feb 1, 2021
It appears my board has a newer chip revision, which explains why your compilation of mdloader doesn't recognize the board. So I would need to build my own mdloader with the latest release, and merge the master branch with the PR branch which I have no idea on how to accomplish.
TwYee
3
Feb 24, 2021
Does this only work for the default_md keymap? Can this work for other keymaps such as endgame?
TiggaTheChigga
0
Aug 9, 2020
same issue with alt
WFAHM
1
Jul 16, 2020
Seriously, no answer?
Dennyh
1
Jun 29, 2020
Also have the same issue with the ALT
Devil_U_Know
80
May 1, 2020
I've just purchased the ctrl and I'm having the same issue, any updates on this?
(Edited)
ibanez
1
Jan 26, 2020
Same issue
yar00001
0
Jan 18, 2020
Any solution for this issue? Also have this problem
bullmoos211
41
Dec 5, 2019
Also having this problem with the CTRL.
japanesecracker
18
Oct 16, 2019
I have the same issue with the ALT.