Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Colormap example does not work #1354

Open
nicos68 opened this issue Aug 22, 2023 · 7 comments
Open

Colormap example does not work #1354

nicos68 opened this issue Aug 22, 2023 · 7 comments
Labels
bug Something isn't working

Comments

@nicos68
Copy link

nicos68 commented Aug 22, 2023

The Colormap.ino source code that can be found under examples/LEDs/Colormap does not behave as expected.

Steps to reproduce the behavior:

  • Compile the source code of Colormap.ino
  • Flash the binary to the keyboard

Expected behavior

  • The colors defined in the Colormap.ino source code are applied to the keyboard's LEDs

Actual behavior

  • Seemingly random colors are applied to the keyboard's LEDs.
  • When running Chrysalis the colors displayed by the tool acutally match the keyboard LEDs' colors:
    image
  • after a few seconds the LEDs of the keyboard's right half turn off.
  • If I use chrysalis to change a led color, it actually gets applied to the keyboard's LEDs

Environment (please complete the following information):

  • OS: Fedora
  • Version 38
  • Device Keyboardio Model 01

Additional context

  • When doing a factory reset, no matter what color I set using Chrysalis, it never gets applied to the keyboard's LEDs
  • No matter what colors I pass to the COLORMAP function call as argument on line 80, the same random colors get applied to the keyboard.
@nicos68 nicos68 added the bug Something isn't working label Aug 22, 2023
@nicos68
Copy link
Author

nicos68 commented Mar 24, 2024

So it looks like I have to run the backup script after flashing for the colormap plugin to work, that’s confusing but well, I found a solution.

@obra
Copy link
Member

obra commented Mar 25, 2024 via email

@nicos68
Copy link
Author

nicos68 commented Mar 25, 2024

  • I use kaleidoscope’s eeprom-backup script
  • I flash my keyboard
    • Using Chrysalis when I make simple keymap changes
    • Using arduino-cli when I make code changes to the firmware. See the flash (and compile) recipe in my justfile

@obra
Copy link
Member

obra commented Mar 25, 2024 via email

@nicos68
Copy link
Author

nicos68 commented Mar 25, 2024

Well, I would expect things to fix themselves when I execute the restore script, but that's not what happens :

  • I added the colormap plugin to my firmware code
  • I compiled the firmware
  • I flashed the new firmware with colormap and my color settings => The random colors showed up and my colormap settgins were ignored
  • I ran the backup scrip => then immidiately my colormap settings were applied to the keyboard. I did not run the restore script.

@obra
Copy link
Member

obra commented Mar 25, 2024 via email

@nicos68
Copy link
Author

nicos68 commented Mar 26, 2024

It works like that everytime now. If I change the colormap in my firmware, then compile and flash, the color change is ignored. Then when I run the backup script the colormap change is correctly applied.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants