qmk_firmware/keyboards/bfake
fauxpark 3a215195ed Convert remaining PS2AVRGB boards to I2C WS2812 driver (#7245)
* Convert remaining PS2AVRGB boards to I2C WS2812 driver

* Add back functions to make the custom matrices happy
2019-11-03 14:43:13 -08:00
..
keymaps
bfake.c Convert remaining PS2AVRGB boards to I2C WS2812 driver (#7245) 2019-11-03 14:43:13 -08:00
bfake.h
config.h
info.json
matrix.c
readme.md
rules.mk Convert remaining PS2AVRGB boards to I2C WS2812 driver (#7245) 2019-11-03 14:43:13 -08:00
usbconfig.h

B.fake

A 60% keyboard with RGB. The B.fake pcb is a copy of the B.face PCB sold by winkeyless. However, the switch matrix is actually the same as the FaceW, a ps2avr PCB sold on mechanicalkeyboards.com.

Keyboard Maintainer: QMK Community
Hardware Supported: B.fake PCB
Hardware Availability: https://www.aliexpress.com/store/product/bface-60-RGB-underground-copy-pcb-from-china-gh60-pcb-Customize-keyboard-PCB/2230037_32731084597.html

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

make bfake:default

Flashing

ps2avr(GB) boards use an atmega32a microcontroller and a different bootloader. It is not flashable using the regular QMK methods.

Windows:

  1. Download HIDBootFlash.
  2. Place your keyboard into reset.
  3. Press the Find Device button and ensure that your keyboard is found.
  4. Press the Open .hex File button and locate the .hex file you created.
  5. Press the Flash Device button and wait for the process to complete.

macOS:

  1. Install homebrew by typing the following:

    /usr/bin/ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)"
    
  2. Install crosspack-avr.

    brew cask install crosspack-avr
    
  3. Install the following packages:

    brew install python
    brew install pyusb
    brew install --HEAD`https://raw.githubusercontent.com/robertgzr/homebrew-tap/master/bootloadhid.rb
    
    
  4. Place your keyboard into reset.

  5. Flash the board by typing bootloadHID -r followed by the path to your .hex file.

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