jlj-qmk/keyboards/jj40
Kenneth Aloysius 365b863578 Backlighting for JJ40 and underglow initialisation code (#2260)
* Cleanup Mechmini keymap. Once the custom RGB function is defined, there is no need to manually handle RGB code.

* Change default to KEYMAP_MIT, not KEYMAP_OFFSET

* Add custom RGB code for JJ40

* Reset Mechmini advertised power draw to 500. Will have to test actual maximum power draw later.

* RGB working on JJ40.

* Fix: saturation increase/decrease flipped

* Add new directory for my custom keymap with RGB keycodes

* Swap LAlt and LGUI

* Update JJ40 max power draw with measured value

* Update: fun40 rules.mk to enable underglow; earlier failed Travis CI

* Fix: init RGB LEDs on boot. Also added HHKB-like keymap for XD60.

* Super rudimentary backlight test, init RGB LEDs on boot

* Backlighting works - stays on for now

* Toggling working

* Now can override backlight.c functions. Problem was functions in backlight.c weren't called before due to a lack of matrix_scan_quantum() in matrix.c

* Timers not working

* Delete global.h

* Cleanup

* Compiles

* Good sign: LEDs stop working again

* Handle timer1 overflow

* Progress: fix: forgot to init

* Backlighting fully working now except breathing.

* Revert keymap to original keycodes

* Update XD60 keymap README

* Update JJ40 keymap with backlight toggles

* Breathing working just fine.

* Update references

* Add backlight_set() call

* Cleanup code to disable backlight

* Fix: does not compile

* Fix: missing call to rgblight_task.

* Testing with BACKLIGHT_BREATHING

* Cleanup

* Cleanup comments

* More commenting cleanup.

* Do not enable BACKLIGHT_BREATHING by default
2018-01-18 16:02:32 -05:00
..
keymaps Backlighting for JJ40 and underglow initialisation code (#2260) 2018-01-18 16:02:32 -05:00
tools
backlight_custom.h Backlighting for JJ40 and underglow initialisation code (#2260) 2018-01-18 16:02:32 -05:00
backlight.c Backlighting for JJ40 and underglow initialisation code (#2260) 2018-01-18 16:02:32 -05:00
breathing_custom.h Backlighting for JJ40 and underglow initialisation code (#2260) 2018-01-18 16:02:32 -05:00
config.h Backlighting for JJ40 and underglow initialisation code (#2260) 2018-01-18 16:02:32 -05:00
i2c.c
i2c.h
jj40.c Backlighting for JJ40 and underglow initialisation code (#2260) 2018-01-18 16:02:32 -05:00
jj40.h Backlighting for JJ40 and underglow initialisation code (#2260) 2018-01-18 16:02:32 -05:00
matrix.c Backlighting for JJ40 and underglow initialisation code (#2260) 2018-01-18 16:02:32 -05:00
README.md Fixed bootloader access key 2017-11-26 02:22:23 -05:00
rules.mk Backlighting for JJ40 and underglow initialisation code (#2260) 2018-01-18 16:02:32 -05:00
usbconfig.h Backlighting for JJ40 and underglow initialisation code (#2260) 2018-01-18 16:02:32 -05:00

jj40

jj40

A compact 40% (12x4) ortholinear keyboard kit made and KPRepublic on AliExpress.

Keyboard Maintainer: QMK Community
Hardware Supported: Atmega32A
Hardware Availability: AliExpress

Make example for this keyboard (after setting up your build environment):

make jj40:default:program

See build environment setup then the make instructions for more information.

Note that this is a complete replacement for the firmware, so you won't be using Bootmapper Client to change any keyboard settings, since not all the USB report options are supported.

In addition you may need the AVR toolchain and bootloadHID for flashing:

$ brew cask install crosspack-avr
$ brew install --HEAD https://raw.githubusercontent.com/robertgzr/homebrew-tap/master/bootloadhid.rb

In order to use the ./program script, which can reboot the board into the bootloader, you'll need Python 2 with PyUSB installed:

$ pip install pyusb

If you prefer, you can just build it and flash the firmware directly with bootloadHID if you boot the board while holding down Backspace (Top Right Key) to keep it in the bootloader:

$ make jj40
$ bootloadHID -r jj40_default.hex

Troubleshooting

  1. Try plugging the board in while pressing Backspace (Top Right Key). This will force it to boot only the bootloader without loading the firmware. Once this is done, just reflash the board with the original firmware.
  2. Sometimes USB hubs can act weird, so try connecting the board directly to your computer or plugging/unplugging the USB hub.
  3. If you get an error such as "Resource Unavailable" when attemting to flash on Linux, you may want to compile and run tools/usb_detach.c. See tools/README.md for more info.