geekhack
geekhack Projects => Making Stuff Together! => Topic started by: sircheddar on Sun, 31 January 2016, 00:35:06
-
I just finished handwiring a keyboard that I designed (67 key keyboard).
I used a teensy 2.0
I have pictures of the pins used on what columns, rows, and the layout.
I really want to finish the project sooner then later as I am burning out on it, but I want to save learning to program the keyboard till I have more time and interest in doing so.
Is this something I could pay someone to do for me? I feel like if someone had experience doing this, it could be quick, but I lack the interest or energy at the moment.
-
oh god, that title...
-
I'm sure you could. Just curious though how long do you think it will take to learn? It might take several hours or it could be fairly quick if you don't have problems. If you pay someone to do the work that would mean youd have to ship it. The whole process could take much longer. And it seems you must have already invested a while in the board hand wiring it. That's probably the most difficult part. But still you can probably find someone around in the classifieds willing to do it. My opinion is that you would be surprised how helpful people are around here and you should consider doing it yourself. Post questions and people will help. :)
-
hi cool,
i was just planning on having them create and compile the code, and send it to me, where i could put it on the teensy.
just have them do the remote coding, and i'd take over the rest.
but thanks for the advice, that is what i may certainly end up doing.
-
If I understand correctly, you can use hasu's TMK firmware as well as matalliqaz' Easy AVR Keymapping tool to program the board.
-
Programming the board shouldn't be more than swapping out some numbers and such. There should be premade layouts too.
-
Ok, I have hopefully finished the editing on the code for my keyboard to work. The final step on matt3o's guide is to compile the code, and I have no idea how to do that. he says open it in the terminal. what is the terminal? is that on winavr, or is that on notepad++, or what... agh i feel so close to being finished but i can't get the last step of course.
-
Ok, I have hopefully finished the editing on the code for my keyboard to work. The final step on matt3o's guide is to compile the code, and I have no idea how to do that. he says open it in the terminal. what is the terminal? is that on winavr, or is that on notepad++, or what... agh i feel so close to being finished but i can't get the last step of course.
'The terminal' is refering to the terminal software of your preference, for example the windows command line. If you're following matt3os guide there's a program in the directory you are using (gh60 in his guide). This program has to be started by executing it by the command 'make -f Makefile'.
-
Dude, don't give up! You already went through all that trouble of hard-wiring your keyboard! Use "Easy AVR" for fast programming, unless you want to learn the nooks and crannies of learning how to build your own firmware.
-
What exactly needs doing? This doesn't sound hard, post the specs :)
-
i've gotten it down to a hex file. when i plug the keyboard in, program the hex file, then reboot, nothing is happening. does that mean its a complete bust, or am i missing a step along the way.
-
At a guess your firmware config has the diodes one way and the board has them the other. If you short the switch pin that's not attached to the diode to the far side of the diode do you get a keypress? That would confirm it.
-
At a guess your firmware config has the diodes one way and the board has them the other. If you short the switch pin that's not attached to the diode to the far side of the diode do you get a keypress? That would confirm it.
what does shorting the switch pin even mean? i just don't really even understand how to confirm anything with this project. the way the diodes are is the way matt3o did his in the guide, with the black strip on the bottom end of them.
-
This guide (http://cubiq.org/build-your-very-own-pc-keyboard)?
All you need to do is touch the pin that's not connected to the diode to the row using something conductive (a piece of wire, tweezers, scissors...) This will bypass the diode and the keyboard will think you pressed the switch.
-
This guide (http://cubiq.org/build-your-very-own-pc-keyboard)?
All you need to do is touch the pin that's not connected to the diode to the row using something conductive (a piece of wire, tweezers, scissors...) This will bypass the diode and the keyboard will think you pressed the switch.
i put the wire on the end of a row and on some of the controls for the teensy and i actually managed to get some input... so what does it mean?
-
http://imgur.com/a/lqr58
-
This guide (http://cubiq.org/build-your-very-own-pc-keyboard)?
All you need to do is touch the pin that's not connected to the diode to the row using something conductive (a piece of wire, tweezers, scissors...) This will bypass the diode and the keyboard will think you pressed the switch.
i put the wire on the end of a row and on some of the controls for the teensy and i actually managed to get some input... so what does it mean?
i put up a crappy picture that i took of the wiring so far.
-
The wiring looks good but as suspected it doesn't match your firmware. It's not built the right way for Easy AVR so no quick fix, but if you post your TMK config someone can probably point out what you need to switch to make it work.
-
The wiring looks good but as suspected it doesn't match your firmware. It's not built the right way for Easy AVR so no quick fix, but if you post your TMK config someone can probably point out what you need to switch to make it work.
#----------------------------------------------------------------------------
# On command line:
#
# make all = Make software.
#
# make clean = Clean out built project files.
#
# make coff = Convert ELF to AVR COFF.
#
# make extcoff = Convert ELF to AVR Extended COFF.
#
# make program = Download the hex file to the device.
# Please customize your programmer settings(PROGRAM_CMD)
#
# make teensy = Download the hex file to the device, using teensy_loader_cli.
# (must have teensy_loader_cli installed).
#
# make dfu = Download the hex file to the device, using dfu-programmer (must
# have dfu-programmer installed).
#
# make flip = Download the hex file to the device, using Atmel FLIP (must
# have Atmel FLIP installed).
#
# make dfu-ee = Download the eeprom file to the device, using dfu-programmer
# (must have dfu-programmer installed).
#
# make flip-ee = Download the eeprom file to the device, using Atmel FLIP
# (must have Atmel FLIP installed).
#
# make debug = Start either simulavr or avarice as specified for debugging,
# with avr-gdb or avr-insight as the front end for debugging.
#
# make filename.s = Just compile filename.c into the assembler code only.
#
# make filename.i = Create a preprocessed source file for use in submitting
# bug reports to the GCC project.
#
# To rebuild project do "make clean" then "make all".
#----------------------------------------------------------------------------
# Target file name (without extension).
TARGET = gh60_lufa
# Directory common source filess exist
TMK_DIR = ../../tmk_core
# Directory keyboard dependent files exist
TARGET_DIR = .
# project specific files
SRC = keymap_common.c \
matrix.c \
led.c
ifdef KEYMAP
SRC := keymap_$(KEYMAP).c $(SRC)
else
SRC := keymap_poker.c $(SRC)
endif
CONFIG_H = config.h
# MCU name
#MCU = at90usb1287
MCU = atmega32u4
# Processor frequency.
# This will define a symbol, F_CPU, in all source code files equal to the
# processor frequency in Hz. You can then use this symbol in your source code to
# calculate timings. Do NOT tack on a 'UL' at the end, this will be done
# automatically to create a 32-bit value in your source code.
#
# This will be an integer division of F_USB below, as it is sourced by
# F_USB after it has run through any CPU prescalers. Note that this value
# does not *change* the processor frequency - it should merely be updated to
# reflect the processor speed set externally so that the code can use accurate
# software delays.
F_CPU = 16000000
#
# LUFA specific
#
# Target architecture (see library "Board Types" documentation).
ARCH = AVR8
# Input clock frequency.
# This will define a symbol, F_USB, in all source code files equal to the
# input clock frequency (before any prescaling is performed) in Hz. This value may
# differ from F_CPU if prescaling is used on the latter, and is required as the
# raw input clock is fed directly to the PLL sections of the AVR for high speed
# clock generation for the USB and other AVR subsections. Do NOT tack on a 'UL'
# at the end, this will be done automatically to create a 32-bit value in your
# source code.
#
# If no clock division is performed on the input clock inside the AVR (via the
# CPU clock adjust registers or the clock division fuses), this will be equal to F_CPU.
F_USB = $(F_CPU)
# Interrupt driven control endpoint task(+60)
OPT_DEFS += -DINTERRUPT_CONTROL_ENDPOINT
# Boot Section Size in *bytes*
# Teensy halfKay 512
# Teensy++ halfKay 1024
# Atmel DFU loader 4096
# LUFA bootloader 4096
# USBaspLoader 2048
OPT_DEFS += -DBOOTLOADER_SIZE=4096
# Build Options
# comment out to disable the options.
#
BOOTMAGIC_ENABLE = yes # Virtual DIP switch configuration(+1000)
MOUSEKEY_ENABLE = yes # Mouse keys(+4700)
EXTRAKEY_ENABLE = yes # Audio control and System control(+450)
CONSOLE_ENABLE = yes # Console for debug(+400)
COMMAND_ENABLE = yes # Commands for debug and configuration
#SLEEP_LED_ENABLE = yes # Breathing sleep LED during USB suspend
NKRO_ENABLE = yes # USB Nkey Rollover - not yet supported in LUFA
# Optimize size but this may cause error "relocation truncated to fit"
#EXTRALDFLAGS = -Wl,--relax
# Search Path
VPATH += $(TARGET_DIR)
VPATH += $(TMK_DIR)
include $(TMK_DIR)/protocol/lufa.mk
include $(TMK_DIR)/common.mk
include $(TMK_DIR)/rules.mk
/*
Copyright 2012 Jun Wako <wakojun@gmail.com>
This program is free software: you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation, either version 2 of the License, or
(at your option) any later version.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License
along with this program. If not, see <http://www.gnu.org/licenses/>.
*/
#ifndef CONFIG_H
#define CONFIG_H
/* USB Device descriptor parameter */
#define VENDOR_ID 0xFEED
#define PRODUCT_ID 0x6060
#define DEVICE_VER 0x0001
#define MANUFACTURER geekhack
#define PRODUCT GH60
#define DESCRIPTION t.m.k. keyboard firmware for GH60
/* key matrix size */
#define MATRIX_ROWS 5
#define MATRIX_COLS 15
/* define if matrix has ghost */
//#define MATRIX_HAS_GHOST
/* Set 0 if debouncing isn't needed */
#define DEBOUNCE 5
/* Mechanical locking support. Use KC_LCAP, KC_LNUM or KC_LSCR instead in keymap */
#define LOCKING_SUPPORT_ENABLE
/* Locking resynchronize hack */
#define LOCKING_RESYNC_ENABLE
/* key combination for command */
#define IS_COMMAND() ( \
keyboard_report->mods == (MOD_BIT(KC_LSHIFT) | MOD_BIT(KC_RSHIFT)) \
)
/*
* Feature disable options
* These options are also useful to firmware size reduction.
*/
/* disable debug print */
//#define NO_DEBUG
/* disable print */
//#define NO_PRINT
/* disable action features */
//#define NO_ACTION_LAYER
//#define NO_ACTION_TAPPING
//#define NO_ACTION_ONESHOT
//#define NO_ACTION_MACRO
//#define NO_ACTION_FUNCTION
#endif
/*
Copyright 2012 Jun Wako <wakojun@gmail.com>
This program is free software: you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation, either version 2 of the License, or
(at your option) any later version.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License
along with this program. If not, see <http://www.gnu.org/licenses/>.
*/
/*
* scan matrix
*/
#include <stdint.h>
#include <stdbool.h>
#include <avr/io.h>
#include <util/delay.h>
#include "print.h"
#include "debug.h"
#include "util.h"
#include "matrix.h"
#ifndef DEBOUNCE
# define DEBOUNCE 5
#endif
static uint8_t debouncing = DEBOUNCE;
/* matrix state(1:on, 0:off) */
static matrix_row_t matrix[MATRIX_ROWS];
static matrix_row_t matrix_debouncing[MATRIX_ROWS];
static matrix_row_t read_cols(void);
static void init_cols(void);
static void unselect_rows(void);
static void select_row(uint8_t row);
inline
uint8_t matrix_rows(void)
{
return MATRIX_ROWS;
}
inline
uint8_t matrix_cols(void)
{
return MATRIX_COLS;
}
void matrix_init(void)
{
// initialize row and col
unselect_rows();
init_cols();
// initialize matrix state: all keys off
for (uint8_t i=0; i < MATRIX_ROWS; i++) {
matrix = 0;
matrix_debouncing = 0;
}
}
uint8_t matrix_scan(void)
{
for (uint8_t i = 0; i < MATRIX_ROWS; i++) {
select_row(i);
_delay_us(30); // without this wait read unstable value.
matrix_row_t cols = read_cols();
if (matrix_debouncing != cols) {
matrix_debouncing = cols;
if (debouncing) {
debug("bounce!: "); debug_hex(debouncing); debug("\n");
}
debouncing = DEBOUNCE;
}
unselect_rows();
}
if (debouncing) {
if (--debouncing) {
_delay_ms(1);
} else {
for (uint8_t i = 0; i < MATRIX_ROWS; i++) {
matrix = matrix_debouncing;
}
}
}
return 1;
}
bool matrix_is_modified(void)
{
if (debouncing) return false;
return true;
}
inline
bool matrix_is_on(uint8_t row, uint8_t col)
{
return (matrix[row] & ((matrix_row_t)1<<col));
}
inline
matrix_row_t matrix_get_row(uint8_t row)
{
return matrix[row];
}
void matrix_print(void)
{
print("\nr/c 0123456789ABCDEF\n");
for (uint8_t row = 0; row < MATRIX_ROWS; row++) {
phex(row); print(": ");
pbin_reverse16(matrix_get_row(row));
print("\n");
}
}
uint8_t matrix_key_count(void)
{
uint8_t count = 0;
for (uint8_t i = 0; i < MATRIX_ROWS; i++) {
count += bitpop16(matrix);
}
return count;
}
/* Column pin configuration
* col: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14
* pin: B4 B5 B6 D7 D4 D2 C7 D5 D1 D0 B7 B3 B2 B1 B0 (Rev.A)
* pin: (Rev.B)
*/
static void init_cols(void)
{
// Input with pull-up(DDR:0, PORT:1)
DDRF &= ;
PORTF |= ;
DDRE &= ;
PORTE |= ;
DDRD &= ~(1<<0 | 1<<1 | 1<<2 | 1<<4 | 1<<5 | 1<<7);
PORTD |= (1<<0 | 1<<1 | 1<<2 | 1<<4 | 1<<5 | 1<<7);
DDRC &= ~(1<<7);
PORTC |= (1<<7);
DDRB &= ~(1<<0 | 1<<1 | 1<< 2 | 1<<3 | 1<<4 | 1<<5 | 1<<6 | 1<<7);
PORTB |= (1<<0 | 1<<1 | 1<< 2 | 1<<3 | 1<<4 | 1<<5 | 1<<6 | 1<<7);
}
static matrix_row_t read_cols(void)
{
return (PINB&(1<<4) ? 0 : (1<<0)) |
(PINB&(1<<5) ? 0 : (1<<1)) |
(PINB&(1<<6) ? 0 : (1<<2)) |
(PIND&(1<<7) ? 0 : (1<<3)) |
(PIND&(1<<4) ? 0 : (1<<4)) |
(PIND&(1<<2) ? 0 : (1<<5)) |
(PINC&(1<<7) ? 0 : (1<<6)) |
(PIND&(1<<5) ? 0 : (1<<7)) |
(PIND&(1<<1) ? 0 : (1<<8)) |
(PIND&(1<<0) ? 0 : (1<<9)) |
(PINB&(1<<7) ? 0 : (1<<10)) |
(PINB&(1<<3) ? 0 : (1<<11)) |
(PINB&(1<<2) ? 0 : (1<<12)) |
(PINB&(1<<1) ? 0 : (1<<13)) |
(PINB&(1<<0) ? 0 : (1<<14));
}
/* Row pin configuration
* row: 0 1 2 3 4
* pin: F1 F4 F5 F6 F7
*/
static void unselect_rows(void)
{
// Hi-Z(DDR:0, PORT:0) to unselect
DDRF &= ~0b11110010;
PORTF &= ~0b11110010;
}
static void select_row(uint8_t row)
{
// Output low(DDR:1, PORT:0) to select
switch (row) {
case 0:
DDRF |= (1<<1);
PORTF &= ~(1<<1);
break;
case 1:
DDRF |= (1<<4);
PORTF &= ~(1<<4);
break;
case 2:
DDRF |= (1<<5);
PORTF &= ~(1<<5);
break;
case 3:
DDRF |= (1<<6);
PORTF &= ~(1<<6);
break;
case 4:
DDRF |= (1<<7);
PORTF &= ~(1<<7);
break;
}
}
/*
Copyright 2012,2013 Jun Wako <wakojun@gmail.com>
This program is free software: you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation, either version 2 of the License, or
(at your option) any later version.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License
along with this program. If not, see <http://www.gnu.org/licenses/>.
*/
#ifndef KEYMAP_COMMON_H
#define KEYMAP_COMMON_H
#include <stdint.h>
#include <stdbool.h>
#include <avr/pgmspace.h>
#include "keycode.h"
#include "action.h"
#include "action_macro.h"
#include "report.h"
#include "host.h"
#include "print.h"
#include "debug.h"
#include "keymap.h"
extern const uint8_t keymaps[][MATRIX_ROWS][MATRIX_COLS];
extern const uint16_t fn_actions[];
/* GH60 keymap definition macro
* K2C, K31 and K3C are extra keys for ISO
*/
#define KEYMAP( \
K00, K01, K02, K03, K04, K05, K06, K07, K08, K09, K0A, K0B, K0C, K0D,K0E, \
K10, K11, K12, K13, K14, K15, K16, K17, K18, K19, K1A, K1B, K1C, K1D,K0E, \
K20, K21, K22, K23, K24, K25, K26, K27, K28, K29, K2A, K2B, K2D,K0E, \
K30, K31, K32, K33, K34, K35, K36, K38, K39, K3A, K3B, K3C, K3D,K0E, \
K40, K41, K42, K45, K4A, K4B, K4C, K4D,K0E,\
) { \
{ KC_##K00, KC_##K01, KC_##K02, KC_##K03, KC_##K04, KC_##K05, KC_##K06, KC_##K07, KC_##K08, KC_##K09, KC_##K0A, KC_##K0B, KC_##K0C, KC_##K0D, KC_##K0E }, \
{ KC_##K10, KC_##K11, KC_##K12, KC_##K13, KC_##K14, KC_##K15, KC_##K16, KC_##K17, KC_##K18, KC_##K19, KC_##K1A, KC_##K1B, KC_##K1C, KC_##K1D, KC_##K0E}, \
{ KC_##K20, KC_##K21, KC_##K22, KC_##K23, KC_##K24, KC_##K25, KC_##K26, KC_##K27, KC_##K28, KC_##K29, KC_##K2A, KC_##K2B, KC_NO, KC_##K2D, KC_##K0E}, \
{ KC_##K30, KC_##K31, KC_##K32, KC_##K33, KC_##K34, KC_##K35, KC_##K36, KC_NO, KC_##K38, KC_##K39, KC_##K3A, KC_##K3B, KC_##K3C, KC_##K3D, KC_##K0E}, \
{ KC_##K40, KC_##K41, KC_##K42, KC_NO, KC_NO, KC_NO, KC_NO, KC_##K45, KC_NO, KC_NO, KC_##K4A, KC_##K4B, KC_##K4C, KC_##K4D, KC_##K0E} \
}
/* ANSI valiant. No extra keys for ISO */
#define KEYMAP_ANSI( \
K00, K01, K02, K03, K04, K05, K06, K07, K08, K09, K0A, K0B, K0C, K0D, \
K10, K11, K12, K13, K14, K15, K16, K17, K18, K19, K1A, K1B, K1C, K1D, \
K20, K21, K22, K23, K24, K25, K26, K27, K28, K29, K2A, K2B, K2D, \
K30, K32, K33, K34, K35, K36, K37, K38, K39, K3A, K3B, K3D, \
K40, K41, K42, K45, K4A, K4B, K4C, K4D \
) KEYMAP( \
K00, K01, K02, K03, K04, K05, K06, K07, K08, K09, K0A, K0B, K0C, K0D, \
K10, K11, K12, K13, K14, K15, K16, K17, K18, K19, K1A, K1B, K1C, K1D, \
K20, K21, K22, K23, K24, K25, K26, K27, K28, K29, K2A, K2B, NO, K2D, \
K30, NO, K32, K33, K34, K35, K36, K37, K38, K39, K3A, K3B, NO, K3D, \
K40, K41, K42, K45, NO, K4A, K4B, K4C, K4D \
)
#define KEYMAP_HHKB( \
K00, K01, K02, K03, K04, K05, K06, K07, K08, K09, K0A, K0B, K0C, K0D, K49,\
K10, K11, K12, K13, K14, K15, K16, K17, K18, K19, K1A, K1B, K1C, K1D, \
K20, K21, K22, K23, K24, K25, K26, K27, K28, K29, K2A, K2B, K2D, \
K30, K32, K33, K34, K35, K36, K37, K38, K39, K3A, K3B, K3D, K3C, \
K40, K41, K42, K45, K4A, K4B, K4C, K4D \
) KEYMAP( \
K00, K01, K02, K03, K04, K05, K06, K07, K08, K09, K0A, K0B, K0C, K0D, \
K10, K11, K12, K13, K14, K15, K16, K17, K18, K19, K1A, K1B, K1C, K1D, \
K20, K21, K22, K23, K24, K25, K26, K27, K28, K29, K2A, K2B, NO, K2D, \
K30, NO, K32, K33, K34, K35, K36, K37, K38, K39, K3A, K3B, K3C, K3D, \
K40, K41, K42, K45, K49, K4A, K4B, K4C, K4D \
)
#endif
#include "keymap_common.h"
const uint8_t PROGMEM keymaps[][MATRIX_ROWS][MATRIX_COLS] = {
/* 0: qwerty */
KEYMAP_ANSI(
ESC, 1, 2, 3, 4, 5, 6, 7, 8, 9, 0, MINS, EQL, BSPC,DEL , \
TAB, Q, W, E, R, T, Y, U, I, O, P, LBRC, RBRC,BSLS,PGUP, \
CAPS,A, S, D, F, G, H, J, K, L, SCLN,QUOT, ENT, PGDN, \
LSFT,Z, X, C, V, B, N, M, COMM,DOT, SLSH, RSFT,UP ,~ , \
LCTL,LGUI,LALT, SPC, FN0, RCTL, LEFT,DOWN,RIGHT),
/* 1: FN 1 */
KEYMAP_ANSI(
ESC ,F1, F2, F3, F4, F5, F6, F7, F8, F9, F10, TRNS, TRNS,TRNS,TRNS, \
TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS, TRNS,TRNS,TRNS , \
TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS, TRNS,TRNS , \
TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS, TRNS,TRNS,TRNS,TRNS, TRNS,TRNS,TRNS,\
TRNS,TRNS,TRNS, TRNS, TRNS,TRNS, TRNS,TRNS,TRNS),
};
const uint16_t PROGMEM fn_actions[] = {
/* Poker Layout */
- = ACTION_LAYER_MOMENTARY(1), // to Fn overlay
};
-
The wiring looks good but as suspected it doesn't match your firmware. It's not built the right way for Easy AVR so no quick fix, but if you post your TMK config someone can probably point out what you need to switch to make it work.
hope i posted the correct files. all of the code is extremely foreign to me and intimidates me.
-
anyone willing to figure this out for me, ill send them a small paypal gift. i am really just needing to get this done, or i will have a bad night.
-
I'm too tired to really look through your code (btw, link it in pastebin next time, so you don't flood the thread), but here's a few tips if you're stuck.
Triple check the number of rows and columns you have, by counting each individual wire. My custom had a strange angled layout so I made a mistake the first time. You probably won't as your layout is quite straight but the possibility is still there.
Make sure all your diodes point in one direction. You can confirm that by looking at the markings and checking to see they are all pointing in the right direction. Having a backwards facing diode is a simple mistake to make.
Make sure all your solder joins are secure. If your soldering wasn't good the first time round, the wires may not attach to the pins securely and may fall off.
When programming the board, ALWAYS TRIPLE CHECK. When you're constructing the matrix, make sure you get the pinouts correct, by looking at the wire and tracing down its path, confirming it leads to the right pin. Make sure your syntax is ONE HUNDRED PERCENT perfect, or else you will be scratching your head for hours down the path. When you're mapping your keys, ALWAYS refer back to your matrix file and your keyboard.
Once you've finished programming the board, do one last check making sure everything is written out properly, you can begin to compile. On windows, if you're following Matt3o's excellent guide, you should have installed winavr (http://sourceforge.net/projects/winavr/). Open up cmd or powershell and cd into the directory you were working in and enter "make -f Makefile" (without quotation marks). If all goes well, the terminal will spew text for anything from seconds to minutes and you should have a file named gh60.hex. If you encountered an error while compiling, carefully read the output of the terminal, and it will likely point out the error. Go to the error and figure out what you did wrong.
Once you've finished compiling, simply launch the Teensy loader application you should have downloaded and set your board to auto, open your hex file and press the reset button on your board. Give your keyboard a test. Success? Congratulations! Failure? Not to worry! Often times if it is a hardware failure it is an easy fix. If it's a problem with your code, as you imply it is, the only thing you can do is read through everything again, and try to figure out where you went wrong. It may be daunting, but it is definitely worth the effort. Just keep on checking, checking, and even more checking and you will eventually figure it out. Have fun!
-
I'm too tired to really look through your code (btw, link it in pastebin next time, so you don't flood the thread), but here's a few tips if you're stuck.
Triple check the number of rows and columns you have, by counting each individual wire. My custom had a strange angled layout so I made a mistake the first time. You probably won't as your layout is quite straight but the possibility is still there.
Make sure all your diodes point in one direction. You can confirm that by looking at the markings and checking to see they are all pointing in the right direction. Having a backwards facing diode is a simple mistake to make.
Make sure all your solder joins are secure. If your soldering wasn't good the first time round, the wires may not attach to the pins securely and may fall off.
When programming the board, ALWAYS TRIPLE CHECK. When you're constructing the matrix, make sure you get the pinouts correct, by looking at the wire and tracing down its path, confirming it leads to the right pin. Make sure your syntax is ONE HUNDRED PERCENT perfect, or else you will be scratching your head for hours down the path. When you're mapping your keys, ALWAYS refer back to your matrix file and your keyboard.
Once you've finished programming the board, do one last check making sure everything is written out properly, you can begin to compile. On windows, if you're following Matt3o's excellent guide, you should have installed winavr (http://sourceforge.net/projects/winavr/). Open up cmd or powershell and cd into the directory you were working in and enter "make -f Makefile" (without quotation marks). If all goes well, the terminal will spew text for anything from seconds to minutes and you should have a file named gh60.hex. If you encountered an error while compiling, carefully read the output of the terminal, and it will likely point out the error. Go to the error and figure out what you did wrong.
Once you've finished compiling, simply launch the Teensy loader application you should have downloaded and set your board to auto, open your hex file and press the reset button on your board. Give your keyboard a test. Success? Congratulations! Failure? Not to worry! Often times if it is a hardware failure it is an easy fix. If it's a problem with your code, as you imply it is, the only thing you can do is read through everything again, and try to figure out where you went wrong. It may be daunting, but it is definitely worth the effort. Just keep on checking, checking, and even more checking and you will eventually figure it out. Have fun!
exciting news. i plugged it in this morning and i got some letters and stuff to work. but it spammed plus signs, equal signs, and not all of the keys worked. but that was really exciting! i might try to redo the entire code tonight if i get repassionate
-
IDK much about TMK cause I couldnt get it to work but I noticed this
#define KEYMAP( \
K00, K01, K02, K03, K04, K05, K06, K07, K08, K09, K0A, K0B, K0C, K0D,K0E, \
K10, K11, K12, K13, K14, K15, K16, K17, K18, K19, K1A, K1B, K1C, K1D,K0E, \
K20, K21, K22, K23, K24, K25, K26, K27, K28, K29, K2A, K2B, K2D,K0E, \
K30, K31, K32, K33, K34, K35, K36, K38, K39, K3A, K3B, K3C, K3D,K0E, \
K40, K41, K42, K45, K4A, K4B, K4C, K4D,K0E,\
)
#define KEYMAP_ANSI( \
K00, K01, K02, K03, K04, K05, K06, K07, K08, K09, K0A, K0B, K0C, K0D, \
K10, K11, K12, K13, K14, K15, K16, K17, K18, K19, K1A, K1B, K1C, K1D, \
K20, K21, K22, K23, K24, K25, K26, K27, K28, K29, K2A, K2B, K2D, \
K30, K32, K33, K34, K35, K36, K37, K38, K39, K3A, K3B, K3D, \
K40, K41, K42, K45, K4A, K4B, K4C, K4D \
)
#define KEYMAP_HHKB( \
K00, K01, K02, K03, K04, K05, K06, K07, K08, K09, K0A, K0B, K0C, K0D, K49,\
K10, K11, K12, K13, K14, K15, K16, K17, K18, K19, K1A, K1B, K1C, K1D, \
K20, K21, K22, K23, K24, K25, K26, K27, K28, K29, K2A, K2B, K2D, \
K30, K32, K33, K34, K35, K36, K37, K38, K39, K3A, K3B, K3D, K3C, \
K40, K41, K42, K45, K4A, K4B, K4C, K4D \
)
The first keymap, which is the one you are using has a trailing comma after K0E
but it doesn't have that comma at the end of the ANSI or HHKB maps