Ported magic_force/mf34 to VIAL #780
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Ported magic_force/mf34 to VIAL. However, the version being sold on Amazon right now (same VID and PID) has a different mcu. Flashing to the original mf34 should work because I didn't touch anything relating to dfu mode or the mcu. The original code has the STM32F072 listed, mine has the APM32F072 (both have identical specs). Flashing with QMK Toolbox doesn't work because it's looking for a different chip. I have only been able to test the one with the APM chip. I'm not familiar enough with QMK to modify or make a new version. And someone wouldn't be able to tell which one they have unless they open up their keyboard. If people have the APM chip they will need to flash using Geehy Programmer instead of QMK Toolbox.