Building Phantom Hardware and Firmware Mods

[MJ45]

I just finished my Phantom, my first keyboard build and it works great. I flashed the firmware with the PHANSIWIN.hex but I use Macs and have no programing knowledge or experiance. Does anybody have a Mac layout hex file they could share? I am going to try to learn to program this Teensy eventually i hope. Thanks, MJ 

[rindorbrot]

Hey guys,

my Phantom PCB arrived at the weekend and since I have to wait for a case and the corresponding plate before I can continue building it, I wanted to prepare the firmware and stuff.

I am using hasu's TMK firmware and it works quite nice.
But I have one little problem that I still need to solve.

The physical layout of my Phantom will be ISO_150 with short right Shift and a 1x FN-key beneath it.

I already defined a corresponding macro for this layout in the keymap.c (copy-paste of ISO_150 and changed the right shift)

Code: [Select]

#define KEYMAP_RIND( \
    K5A,      K5C, K5D, K5E, K5F, K5H, K5I, K5J, K5K, K5L, K5M, K5N, K5O,      K5P, K5Q, K5R, \
    K4A, K4B, K4C, K4D, K4E, K4F, K4G, K4H, K4I, K4J, K4K, K4L, K4M, K4O,      K4P, K4Q, K4R, \
    K3A, K3B, K3C, K3D, K3E, K3F, K3G, K3H, K3I, K3J, K3K, K3L, K3M,           K3P, K3Q, K3R, \
    K2A, K2B, K2C, K2D, K2E, K2F, K2G, K2H, K2I, K2J, K2K, K2L, K2M, K2N,                     \
    K1A, K1B, K1C, K1D, K1E, K1F, K1G, K1H, K1I, K1J, K1K, K1L, K1M, K1N,           K1Q,      \
    K0A, K0B, K0C,                K0G,                     K0L, K0M, K0N,      K0P, K0Q, K0R  \
) KEYMAP( \
    K5A, NO,  K5C, K5D, K5E, K5F, NO,  K5H, K5I, K5J, K5K, K5L, K5M, K5N, K5O, K5P, K5Q, K5R, \
    K4A, K4B, K4C, K4D, K4E, K4F, K4G, K4H, K4I, K4J, K4K, K4L, K4M, NO,  K4O, K4P, K4Q, K4R, \
    K3A, K3B, K3C, K3D, K3E, K3F, K3G, K3H, K3I, K3J, K3K, K3L, K3M, NO,       K3P, K3Q, K3R, \
    K2A, K2B, K2C, K2D, K2E, K2F, K2G, K2H, K2I, K2J, K2K, K2L, K2M, K2N,      NO,  NO,  NO,  \
    K1A, K1B, K1C, K1D, K1E, K1F, K1G, K1H, K1I, K1J, K1K, K1L, K1M, K1N,      NO,  K1Q, NO,  \
    K0A, K0B, K0C, NO,       NO,  K0G, NO,            NO,  K0L, K0M, K0N,      K0P, K0Q, K0R  \
)
I also defined to use the file keymap_rind.h if the layout "rind" is chosen, which works correctly.

here is my keymap_rind.h

Code: [Select]

// Phantom RIND
static const uint8_t PROGMEM keymaps[][MATRIX_ROWS][MATRIX_COLS] = {
    /* 0: qwerty */
    KEYMAP_RIND(\
        ESC,      F1,  F2,  F3,  F4,  F5,  F6,  F7,  F8,  F9,  F10, F11, F12,       PSCR,SLCK,BRK,  \
        GRV, 1,   2,   3,   4,   5,   6,   7,   8,   9,   0,   MINS,EQL, BSPC,      INS, HOME,PGUP, \
        TAB, Q,   W,   E,   R,   T,   Y,   U,   I,   O,   P,   LBRC,RBRC,           DEL, END, PGDN, \
        CAPS,A,   S,   D,   F,   G,   H,   J,   K,   L,   SCLN,QUOT,NUHS,ENT,                       \
        LSFT,NUBS,Z,   X,   C,   V,   B,   N,   M,   COMM,DOT, SLSH,RSFT,FN0,            UP,        \
        LCTL,LGUI,LALT,               SPC,                     RALT,RGUI,RCTL,      LEFT,DOWN,RGHT),
    /* 1: media keys */
    KEYMAP_RIND(\
        TRNS,     TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,      TRNS,TRNS,MSTP, \
        TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,           MPLY,MPRV,VOLU, \
        TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,      MUTE,MNXT,VOLD, \
        TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,                      \
        TRNS,TRNS,TRNS,TRNS,CALC,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,           TRNS,      \
        TRNS,TRNS,TRNS,               TRNS,                    TRNS,APP, TRNS,      TRNS,TRNS,TRNS)
};
static const uint16_t PROGMEM fn_actions[] = {
    [0] = ACTION_LAYER_MOMENTARY(1)
};

Everything I defined works as it should besides the three keys MPLY,MPRV,VOLU, which are on the Fn0 layer over INS, HOME,PGUP,

Without pressing Fn0 Insert, Home and Pgup work as intended. Also the rest of the PCB is physically fine.

Can anybody spot my mistake? Help would greatly be appreciated

Edit:
to be more precise, MPLY, MPRV and VOLU are working, but there are on the wrong keys!
They are shifted one key to the left each.
So MPLY is on Backspace instead of Insert, MPRV on Insert instead of Home and VOLU on Home instead of Pgup...

[Grimey]

Code: [Select]

// Phantom RIND
static const uint8_t PROGMEM keymaps[][MATRIX_ROWS][MATRIX_COLS] = {
    /* 0: qwerty */
    KEYMAP_RIND(\
        ESC,      F1,  F2,  F3,  F4,  F5,  F6,  F7,  F8,  F9,  F10, F11, F12,       PSCR,SLCK,BRK,  \
        GRV, 1,   2,   3,   4,   5,   6,   7,   8,   9,   0,   MINS,EQL, BSPC,      INS, HOME,PGUP, \
        TAB, Q,   W,   E,   R,   T,   Y,   U,   I,   O,   P,   LBRC,RBRC,           DEL, END, PGDN, \
        CAPS,A,   S,   D,   F,   G,   H,   J,   K,   L,   SCLN,QUOT,NUHS,ENT,                       \
        LSFT,NUBS,Z,   X,   C,   V,   B,   N,   M,   COMM,DOT, SLSH,RSFT,FN0,            UP,        \
        LCTL,LGUI,LALT,               SPC,                     RALT,RGUI,RCTL,      LEFT,DOWN,RGHT),
    /* 1: media keys */
    KEYMAP_RIND(\
        TRNS,     TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,      TRNS,TRNS,MSTP, \
        TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,      MPLY,MPRV,VOLU, \
        TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,           MUTE,MNXT,VOLD, \
        TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,                      \
        TRNS,TRNS,TRNS,TRNS,CALC,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,           TRNS,      \
        TRNS,TRNS,TRNS,               TRNS,                    TRNS,APP, TRNS,      TRNS,TRNS,TRNS)
};
static const uint16_t PROGMEM fn_actions[] = {
    [0] = ACTION_LAYER_MOMENTARY(1)
};

Does this fix it?  Looks like you have an extra column in Funtion Row 2 on yours

[rindorbrot]

Nicely spotted Grimey, that fixed it. Thanks!

[Wraul]

Nicely spotted Grimey, that fixed it. Thanks!

Yeah there is a bug in the ISO layout files.
As pointed out here http://geekhack.org/index.php?topic=41989.msg957945#msg957945

I have yet to send hasu a pull request for the fix. And I won't be able until I get home in 2 weeks.
Sorry about that.

[agor]

Finished my Phantom today, it's very nice! Still had to fight my unusual usb driver problems, and only a reinstall of Windows helped, not even deinstalling all unused USB devices in devmgmt..
But the work paid off, it looks really well.
I'm going to take some pictures with actual sunlight tomorrow, artificial light does not do this justice.

[gnubag]

make sure to use usb 2.0 instead of 3.0 when you have driver/compatibility problems.

[agor]

Yeah I did, but it was completely f***ed up. Could not solve the problem, even tried copying drivers from another pc on which it worked fine. Heck, it does work in BIOS, but my old windows just did not want to

[Batmann]

I am trying to dim the leds but I am not very familiar with compiling.
Is there someone who could compile an ANSI with windows key firmware with leds set to something like 35 for me?
that would hel a LOT 

[agor]

Well it ain't that hard - why don't you try it and play with Layouts a little bit? :-)
https://github.com/tmk/tmk_keyboard/blob/master/doc/build.md

[Melvang]

Does anyone know if I was to cut an opening in a Round 1 Phantom plate for the controller would it fit a QFR PCB?  I guess another way to ask is the controller the only thing preventing use of a Phantom plate in a QFR case and PCB?  If it is does anyone have any numbers that I can use to modify a phantom plate to work? 

[Batmann]

Well it ain't that hard - why don't you try it and play with Layouts a little bit? :-)
https://github.com/tmk/tmk_keyboard/blob/master/doc/build.md

Thanks a lot 

[SpAmRaY]

Does anyone know if I was to cut an opening in a Round 1 Phantom plate for the controller would it fit a QFR PCB?  I guess another way to ask is the controller the only thing preventing use of a Phantom plate in a QFR case and PCB?  If it is does anyone have any numbers that I can use to modify a phantom plate to work? 

Why not get a universal plate with the controller area cutout already from WFD?

[Melvang]

I was just trying to save another vet in the forums a couple $$ and I have a phantom plate that I won't be using plus WFD is on vacation until the 27th.

[SpAmRaY]

I was just trying to save another vet in the forums a couple $$ and I have a phantom plate that I won't be using plus WFD is on vacation until the 27th.

No worries!!! I just hated to see a phantom plate get chopped up

But hey, a bucks a buck!!

[Melvang]

Not going to chop it up that bad just want to mod it so it will be compatible for a QFR.  Just needing to know if the key spacing is the same.  And dimensions on the plate for other holes that need to get cut.

[simkev]

Not going to chop it up that bad just want to mod it so it will be compatible for a QFR.  Just needing to know if the key spacing is the same.  And dimensions on the plate for other holes that need to get cut.

the spacing is the same so go ahead and dremel a controller cutout.

[Melvang]

Not going to chop it up that bad just want to mod it so it will be compatible for a QFR.  Just needing to know if the key spacing is the same.  And dimensions on the plate for other holes that need to get cut.

the spacing is the same so go ahead and dremel a controller cutout.

Excellent thank you.  Now just need some measurements for the hole to cut.

[danielucf]

I am experiencing something weird with my Phantom. When I plug it into my computer F4, 6^, T, G, and V do not work. However when I plug it into my tablet through an OTG cable those keys magically work. Any idea what on earth could be causing this? If a trace on COL5 was bad I would assume that the keys would never work period, but they work on one device but not another...

[Melvang]

That is an odd one.  Not sure on that one.

[danielucf]

After more troubleshooting I think I have a bad USB port on the teensy. If I have the cable at an extreme angle pulled away from the PCB then those keys work. I guess it is a good thing that jdcarpe is doing a group buy for teensy controllers right now. Sucks that I have to desolder the entire board to fix it *sigh*

[gnubag]

I am experiencing something weird with my Phantom. When I plug it into my computer F4, 6^, T, G, and V do not work. However when I plug it into my tablet through an OTG cable those keys magically work. Any idea what on earth could be causing this? If a trace on COL5 was bad I would assume that the keys would never work period, but they work on one device but not another...

there were some windows 7 updates that fked things over for me. have you tried to re flash the firmware and/or try the phantom on another pc?

[danielucf]

I am experiencing something weird with my Phantom. When I plug it into my computer F4, 6^, T, G, and V do not work. However when I plug it into my tablet through an OTG cable those keys magically work. Any idea what on earth could be causing this? If a trace on COL5 was bad I would assume that the keys would never work period, but they work on one device but not another...

there were some windows 7 updates that fked things over for me. have you tried to re flash the firmware and/or try the phantom on another pc?

Yea that didn't do it. As a last ditch effort I heated the pin again that effected those keys and now everything works fine *sigh* cold solder joint I guess and when I applied pressure to the USB cable it moved the connection just enough for input to work. Case closed, that was a weird one.

[jonathanyu]

I just soldered my teensy on to my phantom today, but the firmware seems a little bit confusing to me.  Is the any step-by-step tutorial/guide here? or which firmware should I use for ansi 1.50x layout?
Because I found the firmware here https://github.com/BathroomEpiphanies/AVR-Keyboard, but.... it just got ton of file there...

[bpiphany]

phantom_ansi_iso.hex is supposed to be correct, but you probably want to head over to https://github.com/tmk/tmk_keyboard instead. Hasu's firmware is a lot fancier.

[oaklandishh]

Is there any guide or help file on how to program macros? I have everything working except I am unsure on how to make macros work. I saw somewhere in this thread someone used MACRO(MD(KEY),D(KEY2),END)  does this work? is there a way to have it type something without making each key a D(KEY)? Thanks

[damorgue]

Is there any guide or help file on how to program macros? I have everything working except I am unsure on how to make macros work. I saw somewhere in this thread someone used MACRO(MD(KEY),D(KEY2),END)  does this work? is there a way to have it type something without making each key a D(KEY)? Thanks

You are better off asking that question in Hasu's thread about his firmware. I believe MD is mod down and, and other keys just use D for down. Then you have to specify when you release the key etc. There are a few other fuctions which are listed among his help files.

[Glod]

HELP. Anybody! i think i fudged this and i need someone who is familiar with which teensy pins go to which columns--if that is the issue.

This is not my first Phantom but it is my first one i am building for myself.

I did a test of each key by shorting each of the switch connections, better to find this stuff out now than when all the switches are on.

I have 2 columns of keys not working


I have tried reflowing and removing solder and adding more to all teensy pins
I have checked to make sure all diodes are in the correct position

Every time i go to redo the soldering, in hopes that is the problem, i end up exposing more of a couple traces, as shown in the photos; the exposed trace started as a scratch. The trace is NOT come up and is not loose, it is just exposed, my guess it has something to do with the quality of the PCB. Putting a meter to it shows the area is still good.

Here is the solder points



This picture is misleading, the burned rosin (is that what it is?) makes a black ring i cant clean off around the solder point, the picture makes it look like the traces are all lifting up but its fine, the pictures above show they are not


Here is the teensy, the more i tried to redo things, the more the teensy got dirty and burned up and it slowly moved away a little bit from the pcb, i would hope it is still good though, it is just those 2 columns that don't work. The teensy on the other phantom i built also kind of looked like this




anyone have any ideas? something a little more precise than me trying to redo everything and making things worse? I'm just about to say this is a $50 loss and losing money is not what i need right now.

[Grimey]

Stuff...

Well having not seen what firmware you are using, I would still guess that two points of connection very close to the teensy are the issue.

My first thought is , did you run pins through the teensy & PCB for the two or three other pins than the two long rows?  I ask this is because I did not on my build at first and my firmware acted up in a similar manner.  I can see that you have a least applied solder to these extra pins holes, but I can't detect if any actually wire was run through it form this angle.

Another this to check would be to make sure the diodes in those columns are all running in the same correct direction. 

Outside of taking a look at the firmware you used, I don't see anything off the top of my head outside of the things above.

[Glod]

i put pins in those three extra holes, they are all soldered to the pcb

i used this firmware
http://geekhack.org/index.php?topic=26742.msg640096#msg640096

i tried all three but the one i used with the other phantom i built was phantom-PHANSIWIN.hex

[MJ45]

i put pins in those three extra holes, they are all soldered to the pcb

i used this firmware
http://geekhack.org/index.php?topic=26742.msg640096#msg640096

i tried all three but the one i used with the other phantom i built was phantom-PHANSIWIN.hex

It looks like you have too much solder & heat on those joints. You could try if you haven't already the diode check as described in the DT wiki Phantom assembly instructions. That is where you test each switch pad to the row & column to the
corresponding pads on the pcb where the Teensy goes. Maybe that might tell you if the problem is on the main pcb or the Teensy pcb, good luck with the problem.   

[Glod]

I realize there is more solder on the teensy because I redid every joint, but even with it like this only those two columns are the ones failing. the heat was on low, I think the brown is mostly the rosin I couldn't clean up. this isn't my first keyboard.

do you know which teensy pins go to which columns? should I redo all the diodes in those columns?

[bpiphany]

Schematics http://deskthority.net/wiki/File:Phantom_schematic.pdf

col_6 -> F0
col_13 -> D6

Honestly, a lot of those connections look very poor. You probably don't want the iron turned down all the way. You want to heat the pads up quickly, adding solder, and move straight out again. I would suggest, sucking the pins clean, or using a braid if you don't have a sucker. Then clean as much gunk as possible off with some solvent before starting over again. You probably wont be able to get the Teensy to come off completely, but that doesn't matter. Remove as much solder as possible, and clean everything up as much as possible. Watch some videos on how soldering should work.  Quick in, quick out, as much heat as fast as possible (within reason).

Edit: This is a bit over the top, but that's the flow you want to do it in

[Glod]

ok ok

i sucked up all the solder i could, i couldnt get it all and the teensy stayed attached to the phantom,

i resoldered every joint on high heat with less solder, i cleaned up before and  soldering and i applied flux with pen before soldering

I get the exact some result. those 2 columns dont work everything else works fine

here is the soldering after redo. The flash photography really brings out every defect......









Grrrrr i really dont want to tell my wife i just threw $50 in the garbage. I wish there was still hope for this thing

[bpiphany]

The only thing you could have screwed up beyond fixing is the Teensy. And that isn't too expensive at least. If you have pointy enough multimeter probes you probably want to check for continuity all the way up to the pads under the ATAmega. That would tell you if you messed something up on the Teensy board. test for continuity and find where the chain is broken. If it isn't there is something wrong with the chip, or the firmware.

Those new solder joints look a lot better =)

Edit: Also make sure the wrong things aren't shorted out to GND or something... On the top of my head I think that should have given the opposite behavior though. Switches being pressed all the time.

[Glod]

i don't see any shorted connections.

i could try checking it with my cheap meter, my hands shake a lot though so im not sure if i can do it.

My only problem with scrapping the teensy is that even after sucking up all the solder it didn't come off because some solder got between the two pcbs, as i elected to solder them so close to each other to fit in a certain keyboard case. it will take a good amount of work to get it off and i am fearing damaging the phantom pcb. But, if is truly the reason i guess i don't have a choice.

i do have another idea to see if it is the teensy! I have a mini breadboard and some cables. i could temporarily connect a fresh teensy to the current connections and see if it works, It would require very little soldering and it would look like a total monster. anyone see any problem with that?

[Glod]

ok so i busted out my meter again but this time actually did it right

something is wrong with the teensy i found

1. F0 was not connected to ATAmega, i scratched the trace with an xacto knife carefully and then directly wired it with a spare wire i had. and what-do-you-know the column for F5 now works!!!! that's one column fixed!
2. B6 was damaged by me it seems, i simply applied a peice of wire to the exposed trace and now we are good. i think this had something to do with the caps lock light not working because now it works
3. D6 though doesn't seem to be hurt, i did a meter continuity test (meter doesn't have many options) and D6 connects to the chip according to the meter. at least some sort of connection exists

So one column fixed, caps lock light fixed, now any suggestions anyone for how to fix the F12 column (col 13?)?


oh here is a picture of my ghetto fix lol,


It looks like crap but it is actually sturdy, if manage to fix this column, i'll be able to save this without trashing the teensy

[Glod]

Holy **** I fixed the teensy, all columns operational.

there was indeed something wrong with D6, i didnt read correctly. i didnt realize it connects through the LED

Along with bpiphany's diagram I used this one http://www.pjrc.com/teensy/atmega32u4.pdf and this one http://www.pjrc.com/teensy/schematic.html (which showed me about the LED.



F0 Fix was scratching trace CAREFULLY with xactro knife near the Atmega and then soldering a wire between that and the F0 pin. Its a mystery to me how F0 was messed up because the trace is on the backside, im sure its my fault and not PJRC

B6 Fix was scratching trace right next to the pin which a connection was severed between them visibly due to bad soldering. l i cut off a small piece of metal from a diode leg that was trimmed off and then soldered it in there

D6 Fix was soldering directly to LED or whatever, like B6 i used a piece of metal from a diode leg. This was probably also my fault why D6 was damaged, it looks burned up around the pin.

everything is sturdy and i saved the teensy, im so happy i danced a little bit!!

Thanks bpiphany for stopping by!

[bpiphany]

Considering the look of your original joints this is awesome work, congratulations =D Hell it's awesome either way, those traces are darn tight.

Side note: In this case it was probably you having destroyed something, since it works for other people. But that LED has screwed me over more than a couple of times by just being there. They really should make it possible to disconnect it altogether..

[MOZ]

This is good to know glod!

[Glod]

so i started typing up a response on my phantom saying the phantom is finished now and working great........
but now the celebration has been halted!, when i press P now the entire row goes off randomly pressing other keys.

nooooooooooooooooo,

what the hell! it was working just a minute ago.  Its only the P key, all other keys are fine, maybe something is shorting i dont know. Its bed time for me, 3AM, i guess ill deal with that tomorrow. I needed to do something to it anyway, one of my blue switches isn't clicky and i was going to swap out switches.


edit: Fixed! time for custom firmware!

edit2: TMK Custom firmware success! Phantom officially complete,

[MOZ]

Time for a TEENSY switch

[Tarzan_]

Congrats on the hardware/firmware fix!

Not to derail the thread, but what is the recommended firmware file for custom keyboards - hardwired Teensy mods?  I thought I saw Hasu had recommended the macway version, but the label on that file on GitHub says "retired."

[Findecanor]

col_13 -> D6

Yep. I found out yesterday that D6 is also connected to the Teensy's on-board LED, so I can't shut off the annoying thing in firmware ...

BTW, the AVR-Keyboard firmware launches the boot loader if you press both Shift keys... which I noticed that I do occasionally when typing.

[Hzza]

BTW, the AVR-Keyboard firmware launches the boot loader if you press both Shift keys... which I noticed that I do occasionally when typing.

Same, I changed mine to lshift, rshift, rcontrol and printscreen I think. No way you're going to press that **** accidentally .

[Melvang]

BTW, the AVR-Keyboard firmware launches the boot loader if you press both Shift keys... which I noticed that I do occasionally when typing.

Same, I changed mine to lshift, rshift, rcontrol and printscreen I think. No way you're going to press that **** accidentally .

[Findecanor]

Same, I changed mine to lshift, rshift, rcontrol and printscreen I think. No way you're going to press that **** accidentally .

I'm thinking of changing it to Caps Lock - LGUI - RGUI for nostalgic reasons...

[Hzza]

Same, I changed mine to lshift, rshift, rcontrol and printscreen I think. No way you're going to press that **** accidentally .

I'm thinking of changing it to Caps Lock - LGUI - RGUI for nostalgic reasons...

lel

I only have one of those keys on my boards with custom firmwares, should make it even more difficult to press .

[nebo]

I'm having a problem with the row 1 on my recent build. When I tested it before putting on the switches everything worked fine, but now not so much.

I have ruled out a few things by now. Went a re-flowed the entire bottom row to be sure the joints were good. No real change. Then for the hell of it I went to rule #1 with electronics, if it doesn't work hit it. By that I mean I pressed a key pretty hard and it registered. So that sounds like something is lose, but all the joints are good (and it's weird that it's exactly only row 1. It really only helps if I push the top part of the switch down (above the stem) and then press the stem. Never seen anything like it.

I currently don't have a multimeter but I doubt that is the problem if the keys do register sometimes.

[Photekq]

So my phantom's all soldered up (except the switches) and is running TMK firmware. I just used jumper wire to confirm all the keys worked, and the greys ones in this picture aren't responding.. Any ideas what could be causing this and what I can do to fix it? Also worth noting I've tried the two firmwares in the OP of this topic, and the phantom is running ANSI 150