-
Notifications
You must be signed in to change notification settings - Fork 6.2k
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
Keyboard sends '=====' after turning on and after flushing firmware #113
Comments
firmware.zip |
Issue doesn't happen with this firmware, what's the difference? Where can I find the config to build it to move to it? BTW - I noticed there are firmwares built that have a certain size and others (built using other zmk repos) that are smaller. This one is of the smaller sizes. What's the difference between those firmwares ?as the file sizes are meaningfully different) around 20-25% difference in the file size. Also interesting, after going back to my firmware, the behavior is different. Now on my Mac when I turn on the keyboard on bluetooth it doesn't generate the autorepeat of equal signs, it only adds a single extra character on the first keypress. Is there any kind of state on the keyboard that gets preserved across firmware updates that can be cleaned? |
The changes in #114 should solve this issue, once the checks pass it can be merged, and then if you run "sync fork" on github it should bring these changes into your branch |
I made the changes manually to my config and it solved all issues above and seems to have solved other firmware flushing issues I did not describe. Thanks! Out of curiosity, can you explain how that change had this effect? Are Kinesis pedals going through the keyboard in the first place? Do you plan to merge it also to your advantage360 branch to later be merged into zmk and other projects that use that branch? |
This is a change to the board definition, it should not apply to the underlying branch. It just adds back some keys for the type C footpedals kinesis sells for the advantage 360 pro. With the problem solved i'm going to close out this issue now, thanks for letting me know it solved your issue :) |
As part of this change you modified |
Apologies, you're correct, this change will be added there as well. I thought you were referring to the base repo that has the custom lighting features |
I have the keyboard for a few weeks now. I face several issues that seem to be related to the same 'family' of issues:
After this initial sequence all works normally until next time I turn off/on the keyboard.
I tried this with the vanilla firmware after building as well as other versions of firmware.
Also, it wasn't always like that, the flushing scenario started a few days after I started using the keyboard, and the turn on scenario started only a few days ago.
Is this normal? Anyone experiencing this as well? Any fix/workaround?
The text was updated successfully, but these errors were encountered: