Adding new pcb with default keymap and personal keymap

[sidcarter]

Description

• Adds the Leeku Finger65 PCB
• Adds a default keymap
• Adds a personal keymap

Majority of the code comes from here - https://github.com/rasmusx/qmk_firmware

Types of Changes

• Core
• Bugfix
• New feature
• Enhancement/optimization
• Keyboard (addition or update)
• Keymap/layout/userspace (addition or update)
• Documentation

Issues Fixed or Closed by This PR

Checklist

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• I have tested the changes and verified that they work and don't break anything (as well as I can manage).

[sidcarter]

To reiterate, not my code. Original code linked in the PR.

I have tested this code with my TX65 and another spare Finger65 PCB that I have.

[fauxpark]

I looked at the tinycmd code a little more, and from what I can tell this board still requires the Jigon software to control the RGB lighting? If this is the case... I don't really know how mergeable this will be. The ATtiny85 looks to have something more sophisticated flashed onto it than the standard Bootmapper RGB controller, as it apparently contains several effects. If there's a way to just send it the raw RGB data, we could potentially strip out everything but that as a custom WS2812 driver. But yeah, this might be tricky.

[sidcarter]

@fauxpark tbqh, the LEDs sit inside an alu case. So I couldn't care less about the LEDs for now.

I'm just glad to have finger65 with QMK on it.

So, I'm happy to strip LEDs from this for now and someone else can add them on when they get a PC or a Acrylic case for the TX65.

So now when I disable all LED stuff, i get this error when compiling. I guess I need to add these in ROW and COL pins - not sure how to do that.

Compiling: quantum/matrix.c                                                                        quantum/matrix.c:51:44: error: ‘MATRIX_ROW_PINS’ undeclared here (not in a function)
 static const pin_t row_pins[MATRIX_ROWS] = MATRIX_ROW_PINS;
                                            ^
quantum/matrix.c:52:44: error: ‘MATRIX_COL_PINS’ undeclared here (not in a function)
 static const pin_t col_pins[MATRIX_COLS] = MATRIX_COL_PINS;

[fauxpark]

Yeah, you need to put something like this in the config.h, under the row/column numbers:

#define MATRIX_ROW_PINS { ... }
#define MATRIX_COL_PINS { ... }

[fauxpark]

Just as a note to the both of us, this and USB_CFG_MAX_BUS_POWER will be configured the same way as for 32U4 keyboards when #7336 lands. 10ms will probably be the default polling interval (as it is for LUFA), but you may want to pre-emptively add #define USB_MAX_POWER_CONSUMPTION 100 into the config.h.

[sidcarter]

done

[sidcarter]

should I also remove the USB_CFG_INTR_POLL_INTERVAL ? @fauxpark

[fauxpark]

The default is turning out to be 1ms, for now, so yeah, that will go too and you should add #define USB_POLLING_INTERVAL_MS 10 in config.h if you want to keep this value. I'll see if I can get my PR in first, then you can remove these two :)

[fauxpark]

@sidcarter okay, the PRs are in, go for it

[noroadsleft]

My stuff's all good. @fauxpark, what say you?

[fauxpark]

Just waiting on these two things, otherwise LGTM

[sidcarter]

https://giphy.com/gifs/doom-dun-dunnn-Py4loHkx4eo1O @fauxpark

[fauxpark]

Thanks!