Can't use/activate modifiers and layers? #140
-
[Using qmk's shell.nix on NixOS with a lily58] I'm not sure if this is a bug or if I've just missed something, but I'm unable to actually activate any of the modifier or layers after going through the setup instructions and flashing. All the base layer keys (alpha, space, enter, period, etc.) work just fine. However, if I hold down any of the modifiers or layer buttons, it just repeats the base key that is at that location. E.g., holding down space and trying to use the directional keys just types " n e i o ". No directional key is actually entered. I haven't modified miryoku_qmk in any way after git fetching and merging it per the readme.org To compile and flash, I just used the basic qmk commands:
Any help is appreciated. |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 2 replies
-
I just wrote a comprehensive answer but my phone ate it and I don't have time now to re-write it. 😅 The short answer is do an EEPROM erase in QMK Toolbox. |
Beta Was this translation helpful? Give feedback.
-
On Linux you can do |
Beta Was this translation helpful? Give feedback.
-
That's normal behaviour for the Tap layer. See https://github.com/manna-harbour/miryoku/tree/master/docs/reference#additional-features. Tap requires a reset or power cycle on master to exit. You can verify you're on the Tap layer by changing the alpha arrangement. E.g. add The keyboard should always start on Base. If it starts on another layer it's because there is a persistent default layer set from the previous firmware. To fix it you can erase the EEPROM with QMK Toolbox on Windows or Mac, or with |
Beta Was this translation helpful? Give feedback.
That's normal behaviour for the Tap layer. See https://github.com/manna-harbour/miryoku/tree/master/docs/reference#additional-features. Tap requires a reset or power cycle on master to exit. You can verify you're on the Tap layer by changing the alpha arrangement. E.g. add
-e MIRYOKU_TAP=QWERTY
to theqmk
command line. See https://github.com/manna-harbour/miryoku/tree/master/docs/reference#tap.The keyboard should always start on Base. If it starts on another layer it's because there is a persistent default layer set from the previous firmware. To fix it you can erase the EEPROM with QMK Toolbox on Windows or Mac, or with
avrdude -p m32U4 -P /dev/ttyACM0 -c avr109 -e
for a pro-micro on Li…