[help] CM Storm liberation device

[nanu]

Hey guys, I've been out of the scene for a long while. Quite easy to do when you're feeling satisfied.

I recently picked up a CM Storm Quickfire Stealth. I would rather its Fn key be a proper Apps/Context Menu key.
So I want to replace the daughterboard on it much like bpiphany's HID Liberation Device, for Filcos. The current plan is to cleanly and minimally wire it to a Teensy++ 2.0 which I have, and then put hasu's or Soarer's firmware on it.

I could also get behind the idea of possibly treating the App key as a Fn key for accessing a layer for keypad keys and the like.

Here's what I have figured out so far, here.

Code: Select all

Cooler Master Quickfire Rapid Stealth pinout and matrix
87 keys, ANSI layout
Model: SGK-4000-GKCM2-US

          1 A B 2                           1 C D 2
   0    CAP o o   Quickfire_V2.1           D- o o D+
   1    SCR o o                           VDD o o GND
   2        o o                      WIN_LOCK o o
   3        o o                               o o
   4        o o                               o o
   5        o o                               o o
   6        o o                               o o
   7        o o                               o o
   8        o o                               o o
   9        o o                               o o
         19     20                         19     20

 87 keys in  8 columns and 18 rows

       A8     A9     B0     B2     B3     B5     B6     B9    
A5     RCtrl         LCtrl  Pause  F5                         
A7            RWin                                            
B1                   PgUp          PgDn                       
B4                   Home          End    UArr          LArr  
B7                   Del                  Space         DArr  
B8                   Ins                                RArr  
C6            RAlt          ScrLk  PrtScr LAlt                
C7                                               LWin         
C8            RShift                             LShift       
C9     Z      A      Tilde  Q      1      Esc    Tab          
D2     Enter  \|     F9            F10    F11    BackSp F12   
D3            :;     -_     P      0      '"     [{     /?    
D4     .>     L      F8     O      9             F7     Apps  
D5     ,<     K      =+     I      8      F6     ]}           
D6     M      J      6      U      7      H      Y      N     
D7     V      F      5      R      4      G      T      B     
D8     C      D      F2     E      3      F4     F3           
D9     X      S      F1     W      2             CapsLk       

	A8	A9	B0	B2	B3	B5	B6	B9
A5	RCtrl		LCtrl	Pause	F5
A7		RWin
B1			PgUp		PgDn
B4			Home		End	UArr		LArr
B7			Del			Space		DArr
B8			Ins					RArr
C6		RAlt		ScrLk	PrtScr	LAlt
C7							LWin
C8		RShift					LShift
C9	Z	A	Tilde	Q	1	Esc	Tab
D2	Enter	\|	F9		F10	F11	BackSp	F12
D3		:;	-_	P	0	'"	[{	/?
D4	.>	L	F8	O	9		F7	Apps
D5	,<	K	=+	I	8	F6	]}
D6	M	J	6	U	7	H	Y	N
D7	V	F	5	R	4	G	T	B
D8	C	D	F2	E	3	F4	F3
D9	X	S	F1	W	2		CapsLk

I lurk the following relevant, recent thread but I'm sort of lost, there, too:
http://deskthority.net/workshop-f7/filc ... t5751.html

What's the next step? I'm looking at various tmk_keyboard ./keyboard examples.
Am I free to pick which pins on the Teensy++ I can map these pins to?

Thoughts in my head:
I think I need 4 PORTs worth of pins.
Is there a GUI or script or the like that can generate the relevant C code?

[damorgue]

Just fyi, I believe bpiphany is working on a daughterboard for it already, or at least he intended to recently. I even belive someone sent him one for him to work on along with a rosewill I believe. I'd check up on that before continuing. If he stopped that, I fully support your endeavor.

[bpiphany]

It's going to be real on Monday I hope, if I didn't botch anything up... The matrix is already mapped out here in the wiki =)

[nanu]

Thanks for letting me know! I normalized my matrix and it matches (at least as wired to a tenkeyless).

BTW, pins 40 and 10 (blank in the matrix on the wiki) route to the Fn key which I desire to be a working APP key.

[bpiphany]

BTW, pins 40 and 10 (blank in the matrix on the wiki) route to the Fn key which I desire to be a working APP key.

Fill it in ;) It will of course be accessible since it is a hole in matrix rows and columns used for other keys. I'm only writing really basic firmwares myself. I leave those tasks to other people =)

[nanu]

BTW, pins 40 and 10 (blank in the matrix on the wiki) route to the Fn key which I desire to be a working APP key.

Fill it in It will of course be accessible since it is a hole in matrix rows and columns used for other keys. I'm only writing really basic firmwares myself. I leave those tasks to other people =)

Done: I added a note below, because depending on reader's intent, the matrix is strictly the layout, or, what key code the original controller sends.

To that end, if they wanted to reuse the original controller, then someone ought to label all the Fn's... I might end up doing that myself, but it's not yet planned..

[bpiphany]

It works! =D Only a few bugs that came out easily...

frosty.JPG (271.96 KiB) Viewed 3330 times

[JBert]

Heh, I love that design.