Part 6: Defining key matrix

1st step
And now, a little bit confusing part, in defining the function of key mapping. I havent finalized this part especially for the fn second layer function, as I'm waiting for my keycap. But the normal keyboard qwerty asdfg zxcvb is already coded and working fine.

I've open keymap_common.h file in the same gh60 directory and look for #define KEYMAP function. Here is the original code



My first reaction was watef*** is this. After further reading, this part is actually simple, though requires lots of attention.
What you see here is the layout design of each keyboard key, and the view is from the top, where all the letters and numbering will be.
Lets take K00 and K12 for example. In K00, the first 0 is for the row, and the second 0 is for the column. So for K12, its mean row 1 columns 2.
Notice that there's no K43, this is due to empty slot in gh60 pcb. K42 is basiccaly alt key, and k45 is spacebar key.

As the program use hex/binary or whatever computer instruction is, the numbering start from 0 till 9, then A, B, C... . Basically A = 10, B = 11, C = 12 and so on. And remember to add comma( , ) and blackslash ( \ ) at the end, and only backslash ( \ ) at the last keyboard layout, as shown in the default code.

Now the second part of the code, its still the same thing, same logic, except that unused slot has to be declare by putting KC_NO.

For my scrappy banger keyboard, since I use a different wiring from gh60 pcb, I've made changes. Forget all the previous numbering method to avoid confusion. I took a look at bottom layout of the keyboard and wiring.


And the view of top part, remember that when you flip from bottom to top view and vice versa, you have make sure of the numbering. Notice the location of K00 and K0D between bottom and top view.


And here is my final code for my scrap banger


******************************** ONLY DO THIS PART IF THERE IS COMPILING ERROR DURING MAKEFILE (in last part)********************

According to matt30, #define KEYMAP_ANSI function can be ignored and no change is needed. But during my compilation of the code, there was lots of error preventing compilation, and log shows that the error comes from function in #define KEYMAP_ANSI , as there is conflict in layout. So I beg to differ, change needed 

So I copy the code from #define KEYMAP function, and paste the whole thing at #define KEYMAP_ANSI . Just copy the content, dont change the function name. This was the changes I've made.



*****************************************************************************************************************************

2nd step
Now time to define what each key does And there is no limitation, what each key does is up to you. As I use Poker 2 layout, I'll be using keymap_poker.c file. Other like keymap_hhkb.c , keymap_hasu.c and so on can also be use, depending on which code suit the keyboard design best.

I would suggest a read on matt3o guide in defining the layout part too as this part are usually comes down to own preferences.

I've made my keymap here, although its a little bit harder to explain, but I'll try my best.
3rd and final step 

Now its time to compile the code and flash it to teensy. I use Windows 8.1 in compiling and WinAvr need to be installed (refer to part 5 for link and fix). After installation, fire up command line console, and then navigate to gh60 folder, and I've compiled the code by typing make -f Makefile



No compilation error, yaaaaay!. I navigate back to gh60 folder, and there it is,  gh60_lufa.hex     

To finish it up, I connect the teensy to PC using mini usb to usb cable (the same adapter on you external hdd), load up teensy loader.


Now to complete the process, I just press the tiny winnie button on teensy, click the auto button, and open the gh60_lufa.hex file in teensy loader. The loader then automatically flash the teensy and reboot teensy.

And for the moment of truth, I fire up notepad, and press the buttons on my scrap banger, and seeing the output on the screen..... ITS DONE! YAAAAAAAAAAY


To sum it up, this project might look complicated at first, but its actually quite do-able even for anyone without programming language background and can be completed within 1 day (took me 2 days because of my stupidity  not checking the firmware code before desoldering back the whole thing).

And you can actually make specific keyboard for specific function, for example like any game with its own specific design keyboard. Hoping that someone else with higher creativity level would come out with their own keyboard design, as this is just a base experiment and guidelines.