TMK keyboard firmware

[hasu]

Hasu, I am using the alps64 hex generator website:

http://www.tmk-kbd.com/tmk_keyboard/editor/alps64/index.html

I cannot get left or right alt keys to work on any layers or keys.  I have tested the all the switches for various other commands, and they seem to work fine.  I even mapped L7 to a key and alt to that same key, but that didn't work. Need my alt + tab T_T

X-post

You cannot do that at this time at least, I have a plan to improve this limitation but not soon.

[alienman82]

removed.

[hasu]

Hasu, I am using the alps64 hex generator website:

http://www.tmk-kbd.com/tmk_keyboard/editor/alps64/index.html

I cannot get left or right alt keys to work on any layers or keys.  I have tested the all the switches for various other commands, and they seem to work fine.  I even mapped L7 to a key and alt to that same key, but that didn't work. Need my alt + tab T_T

X-post

You cannot do that at this time at least, I have a plan to improve this limitation but not soon.

Can building firmware without the tool fix this??

Not sure exactly your problem. Can you post editor URL for your keymap?

[alienman82]

removed.

[TD22057]

Right, no reason to hesitate actionmap except for twice usage of flash memory and conventinalism.

Thanks!  Any thoughts on my questions about features in post 1445?

[firerock]

Hello friends,

I'm currently bringing new life to the old Soviet Izot Magnetic Reed Switch terminal keyboard. For some reasons, I've decided to create the new Teensy-based PCB for this monster.

So, I've got a bunch of very old-fashioned key legend combinations. And following symbol pairs are sharing the same keys: 2 and ", 6 and &, 7 and ', 8 and (, 9 and ), ; and +, : and *. Also, there are @ and ^ at non-shifted positions. How to implement this layout using TMK?

As far as I've got, I could use Fn keys for that purpose. But what I don't understand is how to assign the different meanings for these keys at the normal and shifted positions? Is it possible after all?

Thank you in advance for the answers!

And here is the layout itself, the troublesome keys have red outlines:

[hasu]

Hey hasu,
I'd like to try and support the following features.  Any ideas on if they've been done before or how hard they would be to implement?

1) key to turn oneshot mods on and off for all mods (or a list of mods).  I want to be able to try out oneshot mods for shift, alt, ctrl but I may want to turn them off if I decide I don't like them so I'd like to have a key that globally enables and disables them (using an fn_actions function).

2) oneshot mod when a mod is tapped and normal mod when held - like ACTION_MODS_TAP_KEY( LSFT, LSFT ).  So tap left shift and get a normal oneshot behavior, hold it to get regular shift behavior (oneshot might already work this way - I haven't tried it yet).

3) oneshot layer switch.  Tap FN key which switches to layer 2 and after any key press switches back to layer 1.  Similar to 2) - if FN is held down, layer 2 is active until FN is released - i.e. if FN is held down and another key is pressed, that key from layer 2 is used and the layer switches back to 1 when FN is released but if FN is tapped, then the next key is from layer 2.

I noticed that action_util.h contains these function prototypes but they aren't defined or used anywhere.  I'm guessing these declarations should be removed.

Code: [Select]

void oneshot_toggle(void);
void oneshot_enable(void);
void oneshot_disable(void);


1) Not sure what you want, can you rephrase it with examples?
2) Maybe it is what ACTION_MODS_ONESHOT does. Why don't you try it first?
3) It looks reasonable and useful. Implement it! Not so hard, I think.

As for action_util.h it looks true. Send pull request to https://github.com/tmk/tmk_core if possible.

[chupanibre]

hi, and thanks for making this firmware, it's working great!

i have a question about "ghosting", my keyboard sadly doesn't have diodes for every key.
that means, for example, if i hold "asd" and press "e", my keyboard also sends "qw" although these keys aren't pressed.
is there anything i can do to prevent these false keypresses with software?
i've seen the "MATRIX_HAS_GHOST" parameter, but found no further explanation in the readme files.

it's not a big deal, but if there's an easy fix for this i'd be happy to know!

[hasu]

It should be what you need. Try it and contribute missing document for this.

Sent from my Nexus 5X using Tapatalk

[alienman82]

removed.

[BlueNalgene]

Hello friends,

I'm currently bringing new life to the old Soviet Izot Magnetic Reed Switch terminal keyboard. For some reasons, I've decided to create the new Teensy-based PCB for this monster.

So, I've got a bunch of very old-fashioned key legend combinations. And following symbol pairs are sharing the same keys: 2 and ", 6 and &, 7 and ', 8 and (, 9 and ), ; and +, : and *. Also, there are @ and ^ at non-shifted positions. How to implement this layout using TMK?

As far as I've got, I could use Fn keys for that purpose. But what I don't understand is how to assign the different meanings for these keys at the normal and shifted positions? Is it possible after all?

Thank you in advance for the answers!

And here is the layout itself, the troublesome keys have red outlines:

(Attachment Link)

This sounds like a neat project.  Unfortunately, you cannot change how shift treats keys with TMK afaik.  To do something like that, you would need to write some extra code from scratch telling the firmware to treat the 'shift' key as something like 'shift2'.  You then define in a header the shift2 is actually meant to do all of these crazy things one by one. 

With TMK, you could do something similar quite simply.  What you are looking for are function layers.  You could tell the keyboard to treat the 'shift' key as 'fn1' where fn1 brings up a new layer with the things you want.  You might be able have that second layer give caps versions of the non-special letters by, for example, telling the keyboard when layer fn1 is activated and the "x" key is pressed to send "shift+x".  I'm not sure how you would implement that in the code though.

[hasu]

Hasu, I am using the alps64 hex generator website:

http://www.tmk-kbd.com/tmk_keyboard/editor/alps64/index.html

I cannot get left or right alt keys to work on any layers or keys.  I have tested the all the switches for various other commands, and they seem to work fine.  I even mapped L7 to a key and alt to that same key, but that didn't work. Need my alt + tab T_T

X-post

You cannot do that at this time at least, I have a plan to improve this limitation but not soon.

Can building firmware without the tool fix this??

Not sure exactly your problem. Can you post editor URL for your keymap?

http://bit.ly/1W11EAl

My issue is not a macro.  I cannot get 'alt' to work for any keys on the keyboard

I don't see any ALT on your keymap.

Describe what you want to do and your problem in detail using example, use case or scenario.

Sent from my Nexus 5X using Tapatalk

[alienman82]

removed.

[hasu]

Ha, your keymap works completely to me, lol.
Downloaded your keymap and flashed it on my Alps64 and it works!

Then, your problem is reltated to your hardware, OS setting or ...

[alienman82]

removed.

[chupanibre]

Try it

ok, i simply put the line #define MATRIX_HAS_GHOST in the config.h file and recompiled. turns out that was all i needed to do i wasn't sure if it would work because the (commented) line is not present in the ps2/usb converter code. it doesn't completely solve the problem (only diodes will, i guess), but the situation is slightly improved. most of the "ghosts" are gone. there are still some cases of wrong keypresses, but no more "ghost rows". for example "asd" + "e" now gives me "sdq" (before "asdqwe"). of course, my other keyboard with full nkro gets limited by this as well if i don't recompile the firmware without the parameter..

and contribute missing document for this.

umm.. does the above qualify..?

[hasu]

Oh, wait. are you using converter? You should have said about this first!
Ghost block code doesn't work on converter at all. I'm suprised at the fact your keyboard has no ghost block code, I didn't even know such keyboard exists. It sucks. I'm curious about what your keyboard is in fact.

[skullydazed]

Hello friends,

I'm currently bringing new life to the old Soviet Izot Magnetic Reed Switch terminal keyboard. For some reasons, I've decided to create the new Teensy-based PCB for this monster.

So, I've got a bunch of very old-fashioned key legend combinations. And following symbol pairs are sharing the same keys: 2 and ", 6 and &, 7 and ', 8 and (, 9 and ), ; and +, : and *. Also, there are @ and ^ at non-shifted positions. How to implement this layout using TMK?

As far as I've got, I could use Fn keys for that purpose. But what I don't understand is how to assign the different meanings for these keys at the normal and shifted positions? Is it possible after all?

Thank you in advance for the answers!

And here is the layout itself, the troublesome keys have red outlines:

(Attachment Link)

That's a national layout, and you probably don't want to program the keys to send the US equivalents of those characters.

Quick 10,000 ft view- when you press a key on your keyboard it doesn't send a character. Instead it sends a scan code, which is just a number corresponding to that particular button. Your OS will read that scancode and then convert it to a character. So when you press the number 2 on any keyboard it always sends the same scancode, even if you have a french azerty keyboard that will type é instead.

In your case, you probably want to configure your number row to send the same numbers as any other keyboard. Then you'll need to configure your OS to use a keyboard input language that corresponds to the keyboard you're using.

If you want to design your keyboard so it sends the corresponding characters even while your computer is configured for standard QWERTY input, you will need to define a lot of macros, and replace your shift key with an Fn instead. I do not recommend this approach as you will spend a lot of time putting it together and troubleshooting it to get the behavior right.

[chupanibre]

Oh, wait. are you using converter? You should have said about this first!
Ghost block code doesn't work on converter at all.

well, it does, at least a little. like i said, it improves the ghosting a bit, "worst case" key combinations now only produce one false keypress instead of a row. and in some situations, it successfully blocks the wrong key and delivers the rest. works, but not perfectly.

I'm curious about what your keyboard is in fact.

here's the current (desolate) state of affairs: http://imgur.com/cqUPx1t
i don't have the enclosure, the only lettering on the pcb is "OTC". looks like it's a cousin of the otc ok-keyboard 100m, it has a similar mounting plate but mine has complicated white alps.
it was meant as a testing bed for layouts and keycaps, but i do like the current configuration a lot. all the letter keys had their clicky/tactile plate removed, the rest is unmodified (but cleaned and lubed). and the ghosting thing hasn't been a noticeable issue so far..

also,

It sucks.

hey!!

[firerock]

BlueNalgene, skullydazed, thank you for the valuable info!
OK then, I'll make the standard layout and when everything will work fine, I'll create the custom Windows layout for those peculiar combos.
So, now I have to wait until the PCB will be shipped as well as other parts I've ordered.
And when I'll be done, I'll definitely post my build report!

[TD22057]

FYI - in case anyone cares... I've implemented oneshot mods functions to toggle oneshots mods on and off globally.  The branch is here and the pull request is here.  This allows me to declare all my mods as oneshots and then toggle that behavior on and off with a key on one of my function layers.

This branch implements the following functions to control oneshot behavior and adds an action macro ACTION_MODS_ONESHOT_TOGGLE() to call the toggle function.

    oneshot_toggle()
    oneshot_enable()
    oneshot_disable()

If oneshot is disabled, then any key marked as oneshot behaves normally. When oneshot is enabled (the default), keys marked as oneshot work that way. It does not turn any modifier into a oneshot modifier - only mods marked that way in the action map will work as oneshots. This just allows that behavior to be turned off if desired.

This makes it easy to experiment in a keymap with oneshot modifiers. They can be declared as oneshot mods and another key can be designated to turn the oneshot behavior on and off. So the deciding to use oneshots or not is a software switch controlled from the keyboard instead of requiring a change to the firmware.

[shaymdev]

I'm working with the Adafruit Feather 32u4 Bluefruit LE. pinout and product link

 My end goal is to use TMK with the bluetooth from the board. It's been almost a year since I did this for my first custom build (using a teensy 2)and now I'm having trouble with this microcontroller. As a starting point I'm trying to get TMK working with the "onekey" keyboard but I can't even get that working. I'm using the onekey from tmk as of a day ago (with one change to use pin f0 and f1).

I'm using avrdude to program the board with the hex file. When I push the bootloader button on the board and run lsusb I see the board

Code: [Select]

Bus 003 Device 046: ID 239a:000c
but once the device is programmed I don't get anything in lsusb for it and I can't get hid_listen to find the device (just continues waiting for a device).
I'm on Ubuntu 14.04. I've created the /etc/udev/rules.d/52-tmk-keyboard.rules with the following:

Code: [Select]

SUBSYSTEMS=="usb", ATTRS{idVendor}=="feed", MODE:="0666".

My other keyboard that's got tmk on a teensy is showing up in lsusb and can be read by hid_listen.

When use the same programming commands and push a hex I built from the adafruit tutorials with the arduino ide I can successfully program the board (it'll show in lsusb with the same 239a:000c entry as above and connect it via bluetooth to my phone). This leads me to believe it's maybe an issue with the udev type stuff. Oh, and when I plug it into a windows machine I get "usb device not recognized" errors.

Any suggestions would be greatly appreciated.

[hasu]

what Mhz Xtal does that product has? did you check its frequency?
Many projects in TMK is assuming it is 16MHz.

[shaymdev]

After days of trying and reading I decide to post the question then find a solution 2 minutes later...

Sounds like one of these. http://www.adafruit.com/products/2661

Probably need to set the CPU frequency to 8Mhz in your makefile.

hrm... just tried setting: 

F_CPU = 8000000

This worked for me! Oh it was an exciting moment.

Now I'm going to explore the bluetooth side of things. I'll probably start by using the bluetooth hid tutorial from adafruit and see what kind of integration I can get with tmk. From what I can tell this type of stuff hasn't been done yet (my searches have indicated some people starting to look into but not getting very far). If I'm reinventing the wheel please let me know!

edit: woah, and I was ninja post'd by hasu. Thanks, for your lightning speed!

[TD22057]

Has anyone tried out the chibios version on a Teensy 3.2?  I've been struggling all afternoon to solder D+ and D- to the mini usb connector on my Teensy 2.0 (I don't have enough space in my case for the giant connector that's in the mini usb cables) and have basically given up.  The 3.2 has the USB connectors as pads on the bottom which would solve this in a trivial fashion if I can use it.

[a-c]

Has anyone tried out the chibios version on a Teensy 3.2?  I've been struggling all afternoon to solder D+ and D- to the mini usb connector on my Teensy 2.0 (I don't have enough space in my case for the giant connector that's in the mini usb cables) and have basically given up.  The 3.2 has the USB connectors as pads on the bottom which would solve this in a trivial fashion if I can use it.

Would something like what they do on the ergodox work? https://keyboard-configurator.massdrop.com/ext/ergodox/assembly.php Scroll down to step 7.

[TD22057]

Would something like what they do on the ergodox work? https://keyboard-configurator.massdrop.com/ext/ergodox/assembly.php Scroll down to step 7.

That's what I've been trying.  I cut up different USB cables and they were both a little larger than the one shown there which is bigger than my case can deal with.  I need a solution that doesn't have the large metal connector.  I managed to pull out the plastic tray the pins sit in inside that connector but the solder points are very small and I can't get a reliable connection to it.  My soldering skills just aren't as good as I thought they were...

[Eszett]

I'd like to have rows as "output high", and cols as "input low", how do i have to alter these two passages of the code?

Code: [Select]

static matrix_row_t read_cols(void)
{
    return (PINB&(1<<3) ? 0 : (1UL<<0)) |
           (PINB&(1<<2) ? 0 : (1UL<<1)) |
           (PINB&(1<<1) ? 0 : (1UL<<2)) |
           (PINB&(1<<0) ? 0 : (1UL<<3)) |
           (PINC&(1<<7) ? 0 : (1UL<<4)) |
           (PINF&(1<<0) ? 0 : (1UL<<5)) |
           (PINF&(1<<1) ? 0 : (1UL<<6)) |
           (PINF&(1<<4) ? 0 : (1UL<<7)) |
           (PINF&(1<<5) ? 0 : (1UL<<) |
           (PINF&(1<<6) ? 0 : (1UL<<9)) |
           (PINF&(1<<7) ? 0 : (1UL<<10)) |
           (PINC&(1<<6) ? 0 : (1UL<<11)) |
           (PINB&(1<<6) ? 0 : (1UL<<12)) |
           (PINB&(1<<5) ? 0 : (1UL<<13)) |
           (PINB&(1<<4) ? 0 : (1UL<<14)) |
           (PIND&(1<<7) ? 0 : (1UL<<15)) |
           (PIND&(1<<6) ? 0 : (1UL<<16)) ;
}
and

Code: [Select]

static void unselect_rows(void)
{
    DDRD  &= ~0b00101111;
    PORTD &= ~0b00101111;
}


[rondg]

Hi there!

I am planning to make a keyboard and use TMK for the firmware. The layout will be similar to lightsaver. If I plan to add in-switch/underglow leds,  later on the build, how do I go about the keyboard matrix? I believe that the layout is 19x6, with approx 100 keys. Will it be simpler to use Teensy++ 2.0? Or should I just use Teensy 2.0 and make a 10x10 matrix? Is there a better approach?

[alexjd99]

So I've been trying to figure out how to use this for a while to program my gh60, and I've looked all over for tutorials, and I still can't figure out how to use this at all. I have all the files downloaded and everything sorted out, but I can't figure out how to make my own layout for the life of me.

Does anyone have any recommendation on a tutorial/guide on how to use this? I'm pretty confused with everything after trying for a few days and making no progress at all (I'm also using windows so preferably a windows guide)

[RavenII]

So I've been trying to figure out how to use this for a while to program my gh60, and I've looked all over for tutorials, and I still can't figure out how to use this at all. I have all the files downloaded and everything sorted out, but I can't figure out how to make my own layout for the life of me.

Does anyone have any recommendation on a tutorial/guide on how to use this? I'm pretty confused with everything after trying for a few days and making no progress at all (I'm also using windows so preferably a windows guide)

Well, for starters, what does "Everything sorted out" mean? You've got all your prereqs installed? Compiler, etc? What OS are you on? What have you tried?

[netdudeuk]

Hi

I'm using the IBM Model M version of the TMK code to try and hook up an old USB keyboard with a PS2 adapter to my PC via an Arduino Micro and an Adafruit EZ-Key.

I can pair ok and send key presses from the pre-programmed input pins.

The keyboard looks to be reset by the Micro and I see this in the debugging output -

started logging
[ Initializing PS2 matrix ]
setting global host driver
wFF [ack]
RESET_RESPONSE: rAA [ok]
KBD_ID:

Adafruit Bluefruit HID v1.2 5/12/2014

Attempt to connect to 9,dd,500e7e
Connected
NL:Y CL:N SL:N


When I press the main ENTER key, I get loads of output like this -


r5A rF0
CODESET_QUERY: wF0 [ack] w00 [codeset] FA [ack]
CODESET_RESPONSE: r02 02 [ok]
CODESET_REQUEST: wF0 [ack] w03 [ok]
CODESET_QUERY: wF0 [ack] w00 [codeset] FA [ack]
CODESET_RESPONSE: r02 02 [ok]
CODESET_REQUEST: wF0 [ack] w03 [ok]
CODESET_QUERY: wF0 [ack] w00 [codeset] FA [ack]
CODESET_RESPONSE: r02 02 [ok]
CODESET_REQUEST: wF0 [ack] w03 [ok]
CODESET_QUERY: wF0 [ack] w00 [codeset] FA [ack]
CODESET_RESPONSE: r02 02 [ok]
CODESET_REQUEST: wF0 [ack] w03 [ok]
CODESET_QUERY: wF0 [ack] w00 [codeset] FA [ack]
CODESET_RESPONSE: r02 02 [ok]
CODESET_REQUEST: wF0 [ack] w03 [ok]

and so on ...


I don't get a key press on the PC but the 5A F0 is encouraging as they do seem to relate to this ENTER key.

Any idea what the rest of the debug output implies and why I don't see the key press ?

Thanks

[hasu]

UPDATE:
papodaca's XT to USB converter was merged now.
https://github.com/tmk/tmk_keyboard/pull/355

https://github.com/tmk/tmk_keyboard/tree/master/converter/xt_usb

[Hypersphere]

I have a 60% keyboard with the Hasu Alps64 PCB, and I wish to use the excellent TMK editor to create a HHKB-like layout. However, I have been unsure what to do with two things:

1. How to designate keys that are on the editor map but not on my keyboard (such as the split Backspace and split left and right Shift keys).

2. How to designate a Fn key. For example, I would like to remap the RCtrl as Fn.

I have been told by a very knowledgeable source that for (1) I can either do nothing or use the "NO" designation. Likewise, for (2), I have been told to use L1 for Fn for layer 1, L2 for Fn for layer 2, etc. This certainly makes logical sense, but I wanted to check because the documentation can seem confusing for new users.

UPDATE: After some false starts trying to flash the chip with FLIP for Windows, I was about to move over to my Linux box, but I got things working. My first hex file was not quite correct, but I re-did it, and SUCCESS! I now have a custom brown Alps 60% board with a HHKB layout, complete with media controls.

For reasons unknown the Esc key is unresponsive, which I think is a hardware problem with the board, but I made a new Esc key by mapping Fn+E --> Esc.

Full programmability is definitely the way to go with keyboards. I hope that keyboard companies will start incorporating fully programmable chips using either TMK or their own systems for programming.

In any event, Thanks, Hasu! You have created a marvelous tool and made it relatively easy to use.

[climbalima]

Would adding laptop trackpad support work in the same way as trackpoint support?

[nephiel]

Would adding laptop trackpad support work in the same way as trackpoint support?

A touchpad? If it uses PS/2, then it should probably just work as a mouse, but some features such as multitouch or edge scrolling may not work.

[climbalima]

Would adding laptop trackpad support work in the same way as trackpoint support?

A touchpad? If it uses PS/2, then it should probably just work as a mouse, but some features such as multitouch or edge scrolling may not work.

Yeah. the only issue is that I cannot find the reset pin

[Kaibz]

I've been using tmk firmware with a teensy 2.0++ for more than a year now, however there is still something i don't understand.

About 1 time out of five, when i launch my computer (windows 7), with the keyboard connected, i get this screen:



Of course each time i have to choose "starts windows normally" and unplug the keyboard until windows is loaded, but is there a way to prevent this screen to show up ?

I know it's link to the keyboard as it does not happen if it is unplugged. I even tried changing the teensy, disabling NKRO....I just don't know what to do, please help !

[deductivemonkee]

I keep getting the error while compiling:

Code: [Select]

C:\Users\Matt\Desktop\tmk\keyboard\alps64>make flip
The system cannot find the path specified.
The system cannot find the path specified.
The system cannot find the path specified.
ECHO is off.
mkdir -p obj_alps64
Compiling C: keymap_plain.c
avr-gcc -c -mmcu=atmega32u2 -gdwarf-2 -DF_CPU=16000000UL -DINTERRUPT_CONTROL_ENDPOINT -DNO_LIMITED_CONTROLLER_CONNECT -DBOOTLOADER_SIZE=4096 -DF_USB=16000000UL -DARCH=ARCH_AVR8 -DUSB_DEVICE_ONLY -DUSE_FLASH_DESCRIPTORS -DUSE_STATIC_OPTIONS="(USB_DEVICE_OPT_FULLSPEED | USB_OPT_REG_ENABLED | USB_OPT_AUTO_PLL)" -DFIXED_CONTROL_ENDPOINT_SIZE=8  -DFIXED_NUM_CONFIGURATIONS=1 -DPROTOCOL_LUFA -DBOOTMAGIC_ENABLE -DMOUSEKEY_ENABLE -DMOUSE_ENABLE -DEXTRAKEY_ENABLE -DCONSOLE_ENABLE -DCOMMAND_ENABLE -DVERSION= -Os -funsigned-char -funsigned-bitfields -ffunction-sections -fdata-sections -fno-inline-small-functions -fpack-struct -fshort-enums -fno-strict-aliasing -Wall -Wstrict-prototypes -Wa,-adhlns=obj_alps64/keymap_plain.lst -IC -I/Users/Matt/Desktop/tmk/keyboard/alps64 -IC -I/Users/Matt/Desktop/tmk/tmk_core -IC -I/Users/Matt/Desktop/tmk/tmk_core/protocol/lufa -IC -I/Users/Matt/Desktop/tmk/tmk_core/protocol/lufa/LUFA-git -IC -I/Users/Matt/Desktop/tmk/tmk_core/common -std=gnu99 -include config.h -MMD -MP -MF .dep/obj_alps64_keymap_plain.o.d  keymap_plain.c -o obj_alps64/keymap_plain.o
keymap_plain.c:41:1: fatal error: opening dependency file .dep/obj_alps64_keymap_plain.o.d: No such file or directory
 };
 ^
compilation terminated.
C:/Users/Matt/Desktop/tmk/tmk_core/rules.mk:550: recipe for target 'obj_alps64/keymap_plain.o' failed
make: *** [obj_alps64/keymap_plain.o] Error 1
Any ideas?

[hasu]

I keep getting the error while compiling:

Code: [Select]

C:\Users\Matt\Desktop\tmk\keyboard\alps64>make flip
The system cannot find the path specified.
The system cannot find the path specified.
The system cannot find the path specified.
ECHO is off.
mkdir -p obj_alps64
Compiling C: keymap_plain.c
avr-gcc -c -mmcu=atmega32u2 -gdwarf-2 -DF_CPU=16000000UL -DINTERRUPT_CONTROL_ENDPOINT -DNO_LIMITED_CONTROLLER_CONNECT -DBOOTLOADER_SIZE=4096 -DF_USB=16000000UL -DARCH=ARCH_AVR8 -DUSB_DEVICE_ONLY -DUSE_FLASH_DESCRIPTORS -DUSE_STATIC_OPTIONS="(USB_DEVICE_OPT_FULLSPEED | USB_OPT_REG_ENABLED | USB_OPT_AUTO_PLL)" -DFIXED_CONTROL_ENDPOINT_SIZE=8  -DFIXED_NUM_CONFIGURATIONS=1 -DPROTOCOL_LUFA -DBOOTMAGIC_ENABLE -DMOUSEKEY_ENABLE -DMOUSE_ENABLE -DEXTRAKEY_ENABLE -DCONSOLE_ENABLE -DCOMMAND_ENABLE -DVERSION= -Os -funsigned-char -funsigned-bitfields -ffunction-sections -fdata-sections -fno-inline-small-functions -fpack-struct -fshort-enums -fno-strict-aliasing -Wall -Wstrict-prototypes -Wa,-adhlns=obj_alps64/keymap_plain.lst -IC -I/Users/Matt/Desktop/tmk/keyboard/alps64 -IC -I/Users/Matt/Desktop/tmk/tmk_core -IC -I/Users/Matt/Desktop/tmk/tmk_core/protocol/lufa -IC -I/Users/Matt/Desktop/tmk/tmk_core/protocol/lufa/LUFA-git -IC -I/Users/Matt/Desktop/tmk/tmk_core/common -std=gnu99 -include config.h -MMD -MP -MF .dep/obj_alps64_keymap_plain.o.d  keymap_plain.c -o obj_alps64/keymap_plain.o
keymap_plain.c:41:1: fatal error: opening dependency file .dep/obj_alps64_keymap_plain.o.d: No such file or directory
 };
 ^
compilation terminated.
C:/Users/Matt/Desktop/tmk/tmk_core/rules.mk:550: recipe for target 'obj_alps64/keymap_plain.o' failed
make: *** [obj_alps64/keymap_plain.o] Error 1
Any ideas?

If you are using old WinAVR use other new tool. it doesn't support ATMega32u2 of Alps64 PCB.
If you are editting  keymap_plain.c something is wrong there. Check your change again.

[mrbishop]

having some issues. everything works GREAT except for column 6 which is "5,r,f,c"
when i plug the keyboard in it immediately outputs "
5rfccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccc" until i hit keys to interrupt it
all this was on pin D6
moved to pin C6
same long string output but without firmware update it wont output any key presses but that doesn't surprise me since i haven't flashed it since the pin move.
this feels like a programming issue or two things trying to use that D6 pin

last time i tried to compile i get an error on keymap_plain.c so something is wrong there.

if anyone could help with the errors and weird column issues that would be really awesome. attached is my build folder.

thanks in advance

[a-c]

led.c is conflicting with your matrix B2

having some issues. everything works GREAT except for column 6 which is "5,r,f,c"
when i plug the keyboard in it immediately outputs "
5rfccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccc" until i hit keys to interrupt it
all this was on pin D6
moved to pin C6
same long string output but without firmware update it wont output any key presses but that doesn't surprise me since i haven't flashed it since the pin move.
this feels like a programming issue or two things trying to use that D6 pin

last time i tried to compile i get an error on keymap_plain.c so something is wrong there.

if anyone could help with the errors and weird column issues that would be really awesome. attached is my build folder.

thanks in advance

[deductivemonkee]

I keep getting the error while compiling:

Code: [Select]

C:\Users\Matt\Desktop\tmk\keyboard\alps64>make flip
The system cannot find the path specified.
The system cannot find the path specified.
The system cannot find the path specified.
ECHO is off.
mkdir -p obj_alps64
Compiling C: keymap_plain.c
avr-gcc -c -mmcu=atmega32u2 -gdwarf-2 -DF_CPU=16000000UL -DINTERRUPT_CONTROL_ENDPOINT -DNO_LIMITED_CONTROLLER_CONNECT -DBOOTLOADER_SIZE=4096 -DF_USB=16000000UL -DARCH=ARCH_AVR8 -DUSB_DEVICE_ONLY -DUSE_FLASH_DESCRIPTORS -DUSE_STATIC_OPTIONS="(USB_DEVICE_OPT_FULLSPEED | USB_OPT_REG_ENABLED | USB_OPT_AUTO_PLL)" -DFIXED_CONTROL_ENDPOINT_SIZE=8  -DFIXED_NUM_CONFIGURATIONS=1 -DPROTOCOL_LUFA -DBOOTMAGIC_ENABLE -DMOUSEKEY_ENABLE -DMOUSE_ENABLE -DEXTRAKEY_ENABLE -DCONSOLE_ENABLE -DCOMMAND_ENABLE -DVERSION= -Os -funsigned-char -funsigned-bitfields -ffunction-sections -fdata-sections -fno-inline-small-functions -fpack-struct -fshort-enums -fno-strict-aliasing -Wall -Wstrict-prototypes -Wa,-adhlns=obj_alps64/keymap_plain.lst -IC -I/Users/Matt/Desktop/tmk/keyboard/alps64 -IC -I/Users/Matt/Desktop/tmk/tmk_core -IC -I/Users/Matt/Desktop/tmk/tmk_core/protocol/lufa -IC -I/Users/Matt/Desktop/tmk/tmk_core/protocol/lufa/LUFA-git -IC -I/Users/Matt/Desktop/tmk/tmk_core/common -std=gnu99 -include config.h -MMD -MP -MF .dep/obj_alps64_keymap_plain.o.d  keymap_plain.c -o obj_alps64/keymap_plain.o
keymap_plain.c:41:1: fatal error: opening dependency file .dep/obj_alps64_keymap_plain.o.d: No such file or directory
 };
 ^
compilation terminated.
C:/Users/Matt/Desktop/tmk/tmk_core/rules.mk:550: recipe for target 'obj_alps64/keymap_plain.o' failed
make: *** [obj_alps64/keymap_plain.o] Error 1
Any ideas?

If you are using old WinAVR use other new tool. it doesn't support ATMega32u2 of Alps64 PCB.
If you are editting  keymap_plain.c something is wrong there. Check your change again.

I was using cygwin and flip. I will check my code and report back

[mrbishop]

led.c is conflicting with your matrix B2

having some issues. everything works GREAT except for column 6 which is "5,r,f,c"
when i plug the keyboard in it immediately outputs "
5rfccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccc" until i hit keys to interrupt it
all this was on pin D6
moved to pin C6
same long string output but without firmware update it wont output any key presses but that doesn't surprise me since i haven't flashed it since the pin move.
this feels like a programming issue or two things trying to use that D6 pin

last time i tried to compile i get an error on keymap_plain.c so something is wrong there.

if anyone could help with the errors and weird column issues that would be really awesome. attached is my build folder.

thanks in advance

i noticed that, and yes it needs to be corrected but would that effect the D6 pin or the other pins in this column's keys? that particular row's keys work fine. but i agree it needs to be fixed.

[mrbishop]

led.c is conflicting with your matrix B2

having some issues. everything works GREAT except for column 6 which is "5,r,f,c"
when i plug the keyboard in it immediately outputs "
5rfccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccc" until i hit keys to interrupt it
all this was on pin D6
moved to pin C6
same long string output but without firmware update it wont output any key presses but that doesn't surprise me since i haven't flashed it since the pin move.
this feels like a programming issue or two things trying to use that D6 pin

last time i tried to compile i get an error on keymap_plain.c so something is wrong there.

if anyone could help with the errors and weird column issues that would be really awesome. attached is my build folder.

thanks in advance

i noticed that, and yes it needs to be corrected but would that effect the D6 pin or the other pins in this column's keys? that particular row's keys work fine. but i agree it needs to be fixed.

flashed the firmware with the C6 pin move and the LED B2 pin changed and all seems well now really strange

thanks for all who are looking into this anyway

[a-c]

If this is a Teensy++ there is a LED attached to D6 probably pulled to ground through a resistor.

led.c is conflicting with your matrix B2

having some issues. everything works GREAT except for column 6 which is "5,r,f,c"
when i plug the keyboard in it immediately outputs "
5rfccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccc" until i hit keys to interrupt it
all this was on pin D6
moved to pin C6
same long string output but without firmware update it wont output any key presses but that doesn't surprise me since i haven't flashed it since the pin move.
this feels like a programming issue or two things trying to use that D6 pin

last time i tried to compile i get an error on keymap_plain.c so something is wrong there.

if anyone could help with the errors and weird column issues that would be really awesome. attached is my build folder.

thanks in advance

i noticed that, and yes it needs to be corrected but would that effect the D6 pin or the other pins in this column's keys? that particular row's keys work fine. but i agree it needs to be fixed.

[mrbishop]

it is very much a teensy ++

this is a full key keyboard https://geekhack.org/index.php?topic=82671.0

typing on it now.
thanks again for taking a look and the knowledge about the D6 pin

If this is a Teensy++ there is a LED attached to D6 probably pulled to ground through a resistor.

led.c is conflicting with your matrix B2

having some issues. everything works GREAT except for column 6 which is "5,r,f,c"
when i plug the keyboard in it immediately outputs "
5rfccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccc" until i hit keys to interrupt it
all this was on pin D6
moved to pin C6
same long string output but without firmware update it wont output any key presses but that doesn't surprise me since i haven't flashed it since the pin move.
this feels like a programming issue or two things trying to use that D6 pin

last time i tried to compile i get an error on keymap_plain.c so something is wrong there.

if anyone could help with the errors and weird column issues that would be really awesome. attached is my build folder.

thanks in advance

i noticed that, and yes it needs to be corrected but would that effect the D6 pin or the other pins in this column's keys? that particular row's keys work fine. but i agree it needs to be fixed.

[a-c]

Don't forget to change the bootloader size in the Makefile.

it is very much a teensy ++

this is a full key keyboard https://geekhack.org/index.php?topic=82671.0

typing on it now.
thanks again for taking a look and the knowledge about the D6 pin

[mrbishop]

Don't forget to change the bootloader size in the Makefile.

it is very much a teensy ++

this is a full key keyboard https://geekhack.org/index.php?topic=82671.0

typing on it now.
thanks again for taking a look and the knowledge about the D6 pin

it was changed to the 90USB1268 or were you talking about something else?

update just checked its set to 4096 but eveything is working currently. what are the issues that could become if this is not changed to  Teensy++ halfKay 1024

[a-c]

Using the Bootmagic or Magic key combo to jump to bootloader will probably not work. Convenient if you don't want to leave a hole in your case to access the reset button.

Don't forget to change the bootloader size in the Makefile.

it is very much a teensy ++

this is a full key keyboard https://geekhack.org/index.php?topic=82671.0

typing on it now.
thanks again for taking a look and the knowledge about the D6 pin

it was changed to the 90USB1268 or were you talking about something else?

update just checked its set to 4096 but eveything is working currently. what are the issues that could become if this is not changed to  Teensy++ halfKay 1024