darkkirb/qmk_firmware
1
0
Fork 0
forked from mirrors/qmk_firmware
Code Issues Pull requests Projects Releases Packages Wiki Activity

Update JC65 Readme (#3384)

Browse source
This commit is contained in:
MechMerlin 2018-07-12 10:36:47 -07:00 committed by Drashna Jaelre
parent 1236eac4f2
commit 9c35c5979c
3 changed files with 19 additions and 12 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

7
keyboards/jc65/readme.md
View file

@ -1,10 +1,11 @@
JC65
===
# JC65
![JC65 with 32u4](https://i.imgur.com/I4hCyBI.jpg)
![JC65 with 32a](https://i.imgur.com/9cJ9UbX.jpg)
The JC65 PCB actually has two revisions: A QMK native version, and a PS2AVRGB version. Jchan offered both PCBs as options during the M65-A Round 1 group buy and are now currently available on [keyclack.com](https://keyclack.com/)
The JC65 is the PCB for the Rama M65-A sold through [keyclack.com](https://keyclack.com/). There are two revisions available, a native QMK powered PCB (v32u4) and a PS2AVRGB PCB (v32a), both are available on keyclack.
QMK is supported for both variants.
Make example native QMK version (after setting up your build environment):

14
keyboards/jc65/v32a/readme.md
View file

@ -5,13 +5,15 @@ JC65 ps2avrGB
A 65% keyboard with RGB
Keyboard Maintainer: [Jason Barnachea](https://github.com/nautxx)
Keyboard Maintainer: [Jason Barnachea](https://github.com/nautxx)
Hardware Supported: JC65 rev.ps2avrgb
Hardware Supported: JC65 rev.ps2avrgb
Hardware Availability: [keyclack.com](https://keyclack.com/)
Hardware Availability: [keyclack.com](https://keyclack.com/)
The JC65 PCB actually has two revisions: A QMK native version, and a PS2AVRGB version. Jchan offered both PCBs as options during the M65-A Round 1 group buy, and were also available choices for the 65% acrylic case group buy. In the near future both PCB versions should be available from keyclack.com when the storefront part opens.
The JC65 PCB actually has two revisions: A QMK native version, and a PS2AVRGB version. Jchan offered both PCBs as options during the M65-A Round 1 group buy, and were also available choices for the 65% acrylic case group buy.
Please note that there have been issues with QMK and PS2AVRGB boards. Random shutdowns and overheating have been reported. As of now, the cause has not been discovered.
These docs are for the PS2AVRGB version of the PCB. More info on qmk.fm
@ -23,4 +25,8 @@ Flash example for this keyboard:
bootloadHID -r jc65_v32a_default.hex
Flashing on Windows can be accomplished by downloading [HIDBootFlash](http://vusb.wikidot.com/project:hidbootflash)
To put the PS2AVRGB board into reset, hold down the left control key while plugging in the keyboard.
See [build environment setup](https://docs.qmk.fm/build_environment_setup.html) then the [make instructions](https://docs.qmk.fm/make_instructions.html) for more information.

10
keyboards/jc65/v32u4/readme.md
View file

@ -3,13 +3,13 @@ JC65
![JC65](https://i.imgur.com/I4hCyBI.jpg)
The JC65 PCB actually has two revisions: A QMK native version, and a PS2AVRGB version. Jchan offered both PCBs as options during the M65-A Round 1 group buy, and were also available choices for the 65% acrylic case group buy. In the near future both PCB versions should be available from keyclack.com when the storefront part opens.
The JC65 PCB actually has two revisions: A QMK native version, and a PS2AVRGB version. Jchan offered both PCBs as options during the M65-A Round 1 group buy, and were also available choices for the 65% acrylic case group buy.
These docs are for the QMK version of the PCB. [More info on qmk.fm](http://qmk.fm/planck/)
These docs are for the QMK version of the PCB. [More info on qmk.fm](http://qmk.fm/planck/)
Keyboard Maintainer: [Ethan Madden](https://github.com/jetpacktuxedo)
Hardware Supported: JC65 rev.qmk
Hardware Availability: [keyclack.com](https://keyclack.com/)
Keyboard Maintainer: [Ethan Madden](https://github.com/jetpacktuxedo)
Hardware Supported: JC65 rev.qmk
Hardware Availability: [keyclack.com](https://keyclack.com/)
Make example for this keyboard (after setting up your build environment):