-
-
Notifications
You must be signed in to change notification settings - Fork 10
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
changed arm-gcc-bin to be version 10 #64
Conversation
Is there a particular reason why this change fixes your issue? I'm planning on moving the formula away from I was also not able to get GCC 10 built so there is only 8 and 9: osx-cross/homebrew-arm#29 |
That's a great question I wish I knew the answer to. perhaps a new compile method in general won't have the issue either. And to be fair what I'm doing on on the Keychron K8 (Not pro) isn't exactly supported. I was just trying to contribute back changes that helped me. |
FWIW: arm gcc 10.2 causes the K8 Pro to hard lock. Or at least did, the last time I tested it. So changing the version to fix an issue is just moving around the issue and not actually fixing it. |
Issue is generic on m0, see qmk/qmk_firmware#21228 (comment) |
Since it appears I was using 10.3.1 I'm curious if that issue still stands.
Although back to my previous statement, if |
This is no longer applicable, the formula now uses |
The compiled firmware from MacOS when using SonixQMK on Keychrons seemed to cause an issue if too many keys were pressed or randomly the firmware appeared to just crash and flash some leds sometimes holding the last input.
Description
Updating lines in a couple repos attempting to get this squared away, as pointed out here SonixQMK/qmk_firmware#336
I'm also creating a fork and pull request on the SonixQMK Firmware https://github.com/SonixQMK/qmk_firmware will edit with that pull request.
Pull request on sonixqmkfirmware SonixQMK/qmk_firmware#345