Chuck Lauer Vose
a3104a7110
[Keyboard] Initial commit of Laptreus Keyboard (#4967)
* Add userspace files for vosechu * Code review corrections * Few more code review corrections * Initial add of Laptreus code * Initial add of Laptreus code * Adding last punctuation to default * Add some debug suggestions to the debug readme * Fixes for PR feedback * Fixing capitalization of readme files * update auto detect connection logic |
5 years ago | |
---|---|---|
.. | ||
keymap.c | [Keyboard] Initial commit of Laptreus Keyboard (#4967) | 5 years ago |
readme.md | [Keyboard] Initial commit of Laptreus Keyboard (#4967) | 5 years ago |
This layout is expressly for debugging to see if your keys are working.
NOTE: Make sure you don't have a second QMK keyboard plugged in when you do this!
To compile and flash to the board:
make laptreus:debug:avrdude
To just compile:
make laptreus:debug
Then use QMK toolbox to write the file
Now that you've got the image flashed, do the following:
Open a new text document
Click each key in order and hit enter (with the other keyboard) between each line
For any keys that don't register, hit space (with the other keyboard) and continue on
You'll end up with something looking like this:
a1bcdefghijkl a2bcdefghijkl a3bcdefghijkl a4bcdefghijkl
But almost certainly it won't be perfect, so lets go through some scenarios:
For lines that look like this:
a1bc efg ijkl
Once you have all the keys outputting anything, flash the default layout and do the same thing. If everything is working, your layout will look something like this:
qwertyuiop
asdfghjkl;'
zxcvbnm,./
Note: Don't worry about hitting the backspace or command keys
For lines that look like this:
qwertyyuiop (double y)
For lines that look like this:
qwertyyuiop (t sent t AND y)
For lines that look like this:
qwertgyuiop (t sent t AND g)
qwertgbyuiop (t sent t AND g AND b)