poz/qmk_firmware
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
qmk_firmware/keyboards/jj40
History
ajp10304 added1f062 Planck ajp10304 (#2519) 
* Planck ajp10304 layout clean up

* Planck ajp10304 layout add Mac layer extensions

* JJ40 ajp10304 layout add Mac layer extensions
2018-03-13 02:22:35 -04:00
..
keymaps Planck ajp10304 (#2519) 2018-03-13 02:22:35 -04:00
tools
backlight.c
backlight_custom.h
breathing_custom.h
config.h
i2c.c
i2c.h
jj40.c Fixes for JJ40 and Oscillope keymap (#2496) 2018-03-08 21:31:08 -05:00
jj40.h
matrix.c Update personal layouts, free up matrix_scan_user for JJ40 (#2319) 2018-02-02 01:30:47 -05:00
README.md
rules.mk Update personal layouts, free up matrix_scan_user for JJ40 (#2319) 2018-02-02 01:30:47 -05:00
usbconfig.h

README.md

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.