* change split keyboard tapping term in userspace * fix 5x15 layout numpad movement * minor changes for Nori setup * edit based on 40percentclub refactor change * fix gherkin due to refactor * kbd6x wanleg keymap * kbd6x edits * kbd6x tweak * fn / backlight layer * fix jj40 rgb hex issue * wanleg gherkin lighting * 4x12 layout cleanup * move kbd6x to new kbdfans directory * minor edit related to new kbdfans directory * mac layout for kbd6x * gherkin flip option * tweak tapping term on lets_split * edit for keebio board coalescing * update user readme with git hints * wanleg miniaxe keymap * testing Permissive Hold instead of Mod Tap Interrupt * wiring names * kbd6x keymap * change default backlight behaviour on kbd6x * userspace underglow * userspace underglow * underglow tweaks * user readme update * more layer underglow tweaks * fix userspace for non-underglow-enabled boards * readme edits * readme edits * readme edits * readme edits * Update readme.md * Update readme.md * readme edits * readme edits * update keymap picture
|4 years ago|
|config.h||4 years ago|
|readme.md||4 years ago|
|rules.mk||4 years ago|
|tapdances.c||4 years ago|
|wanleg.c||4 years ago|
|wanleg.h||4 years ago|
- Git Basics
- STM32F103C8T6 Setup
Update a Development Branch
This is how to update a working branch with upstream changes. First we'll update your local master branch. Go to your local project and check out the branch you want to merge into (your local master branch)
$ git checkout master
Fetch the remote, bringing the branches and their commits from the remote repository. You can use the -p, --prune option to delete any remote-tracking references that no longer exist in the remote. Commits to master will be stored in a local branch, remotes/origin/master
$ git fetch -p origin
Merge the changes from origin/master into your local master branch. This brings your master branch in sync with the remote repository, without losing your local changes. If your local branch didn't have any unique commits, Git will instead perform a "fast-forward".
$ git merge origin/master
Checkout the branch you want to merge into
$ git checkout <feature-branch>
Merge your (now updated) master branch into your feature branch to update it with the latest changes from your team.
$ git merge master
This will open your git-configured text editor. Edit the message as desired, save, and exit the editor.
The above steps only update your local feature branch. To update it on GitHub, push your changes.
$ git push origin <feature-branch>
Delete Branch Locally and Remotely
$ git push --delete <remote_name> <branch_name> $ git branch -d <branch_name>
Note that in most cases the remote name is origin.
Delete Local Branch To delete the local branch use one of the following:
$ git branch -d branch_name $ git branch -D branch_name
Note: The -d option is an alias for --delete, which only deletes the branch if it has already been fully merged in its upstream branch. You could also use -D, which is an alias for --delete --force, which deletes the branch "irrespective of its merged status." [Source: man git-branch]
Delete Remote Branch [Updated on 8-Sep-2017] As of Git v1.7.0, you can delete a remote branch using
$ git push <remote_name> --delete <branch_name>
which might be easier to remember than
$ git push <remote_name> :<branch_name>
which was added in Git v1.5.0 "to delete a remote branch or a tag."
Starting on Git v2.8.0 you can also use
git push with the
-d option as an alias for
Therefore, the version of Git you have installed will dictate whether you need to use the easier or harder syntax.
Merge TEST branch into DEV branch
$ git checkout DEV $ git merge TEST $ git push <remote_name> DEV $ git branch -d TEST $ git push <remote_name> :TEST
Note that in most cases the remote name is origin.
The above code will merge, push to remote, and delete both the local and remote TEST branches
Cheap "Blue/Black Pills" typically do not come with a bootloader installed. The Black Pill uses generic_boot20_pb12.bin. The Blue Pill uses generic_boot20_pc13.bin.
The following instructions have been adapted from here.
Flashing a bootloader on to a Black Pill can be done via a USB to Serial converter (e.g. CP2102). This process should be roughly the same for all F103 boards.
- Download the correct bootloader binary
- Set the 'boot 0' pin/jumper high, and 'boot 1' low
B0+ to center pin
B1- to center pin
- Connect the board to the PC using a USB to serial converter
RX to PA9
TX to PA10
GND to Ground
3.3V to 3.3 Volts
- Download and install Flash Loader Demonstrator from here
- Use Flash Loader Demonstrator to flash the bootloader
Ensure the correct COM port is selected. Leave other options with their default values/selections.
Use the "Download to Device" option, with "Erase necessary pages" selected
- After a successful flash, set 'boot 0' pin/jumper low
B0- to center pin
B1- to center pin (no change)
As of April 2019, the
:dfu-util target doesn't work on a *Pill. You will need to use dfu-util directly.
- Use QMK to build your
dfu-util.exe -d 1eaf:0003 -a 2 -D YOUR_FIRMWARE.bin"
If this is the first QMK flash on the *Pill, you will need to synchronize your Reset Button-push with starting the command. By default, the *Pill only stays in bootloader mode for about 3 seconds before returning to normal operation.
See this page if Windows can't see anything to upload to.