localhots
/
qmk_firmware
1
0
Fork 0
Code Releases Activity
qmk_firmware/keyboards/jj40
History
Joe Wasson 743449472e Make `PREVENT_STUCK_MODIFIERS` the default (#3107) 
* Remove chording as it is not documented, not used, and needs work.

* Make Leader Key an optional feature.

* Switch from `PREVENT_STUCK_MODIFIERS` to `STRICT_LAYER_RELEASE`

* Remove `#define PREVENT_STUCK_MODIFIERS` from keymaps.
 		2018-09-17 13:48:02 -04:00
..
keymaps Make `PREVENT_STUCK_MODIFIERS` the default (#3107) 2018-09-17 13:48:02 -04:00
tools Add multiple layout support and Linux flash utility to JJ40 (#1837) 2017-10-13 19:04:36 -10:00
README.md added a description how to flash jj40 in windows (#3247) 2018-06-28 06:52:24 -07:00
backlight.c ps2avrgb: fix incorrect avr ports specified (for numlock and capslock LEDs) (#3453) 2018-07-23 12:11:56 -07:00
backlight_custom.h 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 Add support for the JJ40 Keyboard (#1834) 2017-10-13 10:20:56 -10:00
i2c.h Add support for the JJ40 Keyboard (#1834) 2017-10-13 10:20:56 -10:00
jj40.c Fixes for JJ40 and Oscillope keymap (#2496) 2018-03-08 21:31:08 -05:00
jj40.h Reformat 40% Ortho boards to work with Layouts feature (#2804) 2018-05-14 10:11:12 -04:00
matrix.c Updated matrix.c for some PS2AVRGB boards and templates for new_project script (#2992) 2018-05-31 08:32:05 -07:00
rules.mk Reformat 40% Ortho boards to work with Layouts feature (#2804) 2018-05-14 10:11:12 -04:00
usbconfig.h Backlighting for JJ40 and underglow initialisation code (#2260) 2018-01-18 16:02:32 -05:00

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 (GitHub repo) for flashing:

For macOS:

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

For Linux:

$ sudo apt install libusb-dev
$ wget https://www.obdev.at/downloads/vusb/bootloadHID.2012-12-08.tar.gz
$ tar -xzf bootloadHID.2012-12-08.tar.gz
$ cd bootloadHID.2012-12-08/commandline
$ make
$ sudo cp bootloadHID /usr/bin

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 (or are having issues with a program flash), you can just build it (make jj40:<keymap-name> and flash the firmware (.hex file) 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

For Windows 10: Windows sometimes doesn't recognize the jj40. The easiest way of flashing a new layout is probably using HIDBootFlash.

  1. Go to Windows Device Manager and find the keyboard (plug it in while holding down Backspace (Top Right Key)). It can be found under Human Interface Devices or under Keyboards.
  2. Go to properties and the Details tab to find the hardware ID. You want the VID and the PID (code after the underscore). Plug them into HIDBootFlash and hit Find Device.
  3. Use make jj40:<keymap-name> to generate the .hex file in the qmk basis folder. Select the .hex file in HIDBootFlash and press Flash Device.

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.