* redo make args to use colons, better folder structuring system [skip ci] * don't put spaces after statements - hard lessons in makefile development * fix-up some other rules.mk * give travis a chance * reset KEYMAPS variable * start converting keyboards to new system * try making all with travis * redo make args to use colons, better folder structuring system [skip ci] * don't put spaces after statements - hard lessons in makefile development * fix-up some other rules.mk * give travis a chance * reset KEYMAPS variable * start converting keyboards to new system * try making all with travis * start to update readmes and keyboards * look in keyboard directories for board.mk * update visualizer rules * fix up some other keyboards/keymaps * fix arm board ld includes * fix board rules * fix up remaining keyboards * reset layout variable * reset keyboard_layouts * fix remainging keymaps/boards * update readmes, docs * add note to makefile error * update readmes * remove planck keymap warnings * update references and docs * test out tarvis build stages * don't use stages for now * don't use stages for now
		
			
				
	
	
		
			54 lines
		
	
	
		
			2.1 KiB
		
	
	
	
		
			Markdown
		
	
	
	
	
	
			
		
		
	
	
			54 lines
		
	
	
		
			2.1 KiB
		
	
	
	
		
			Markdown
		
	
	
	
	
	
| # jj40
 | |
| 
 | |
| 
 | |
| 
 | |
| A compact 40% (12x4) ortholinear keyboard kit made and KPRepublic on AliExpress.
 | |
| 
 | |
| Keyboard Maintainer: [QMK Community](https://github.com/qmk)  
 | |
| Hardware Supported: Atmega32A  
 | |
| Hardware Availability: [AliExpress](https://www.aliexpress.com/store/product/jj40-Custom-Mechanical-Keyboard-40-PCB-programmed-40-planck-layouts-bface-firmware-gh40/3034003_32828781103.html)
 | |
| 
 | |
| Make example for this keyboard (after setting up your build environment):
 | |
| 
 | |
|     make jj40:default:program
 | |
| 
 | |
| 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.
 | |
| 
 | |
| 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 `L_Ctrl` to keep it
 | |
| in the bootloader:
 | |
| 
 | |
| ```
 | |
| $ make jj40
 | |
| $ bootloadHID -r jj40_default.hex
 | |
| ```
 | |
| 
 | |
| ## Troubleshooting
 | |
| 
 | |
| 1. Try plugging the board in while pressing `L_Ctrl`. 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.
 |