Apr 28, 2018
Update porting_from_qmk.md
Pre-release

@ahtn ahtn released this Apr 9, 2018 · 141 commits to master since this release

Assets 5

Lots of internal changes. To use this version of the flasher, you'll need to update the firmware on your devices to v0.3.0 first before flashing layouts will work. There's some changes to layout files so that wireless and I2C split are turned off by default, so you'll need to turn the features you were using back on with this settings:

device:
    # ... other settings
    wireless_split: true
    wireless_mouse: true
    wired_split: false
  • Adds new scanning modes row_col, pin_gnd and pin_vcc.
  • Layout updates don't need to reset the USB device, so they are much faster. This feature might still be a little bit buggy. If you have issues updating layouts, you might need to reset your device for some changes to take effect.
  • Cleans up the python back end. You can try it out by downloading the keyplus python package.
  • Adds support for the kp_boot_32u4 bootloader for atmega32u4, and the basis for the atmega32u4 port.

Check out the change log for a more comprehensive list of features.

Assets 4

(NOTE: For REV3 controllers, use v0.3.0 of the flasher instead)

  • Better error messages for bad layout files
  • Corrupt settings detection
  • Error messages tab in keyplus_flasher to read error reports from devices.

@ahtn ahtn released this Jan 20, 2018 · 298 commits to master since this release

Assets 3

This build allows you to pair mice with the receiver. Currently, at this point you can either use the pair keycode to put the device into pairing mode, or run this command keyplus_cli.py pair.

At the moment, to update a unifying receiver already running keyplus, you will need to put it into bootloader mode manually with keyplus_cli.py bootloader and then flash it using the uniflash.py script. This process will be streamlined in the future.

To pair a mouse to a keyplus receiver, first put the receiver into pairing mode. Then while the receiver is in pairing mode, power cycle the mouse you would like to pair. If pairing is successful the receiver should restart as soon as the mouse has paired, and the mouse should be connected. Note, if the mouse you want to pair is in range of a receiver (unifying or keyplus) that it is already paired with, it will not attempt to pair. You will also need to have a valid RF configuration loaded onto the keyplus receiver.

Something that is still being tested is the list of vaild rf_channel's that are used by devices. If you are having trouble connecting your device, try changing the rf_channel in your rf config file to one of these channels: 2, 5, 8, 17, 32, 35, 41, 62, 65, 71.

Pre-release

@ahtn ahtn released this Sep 20, 2017 · 345 commits to master since this release

Assets 5

Add a build that doesn't require the nRF24L01+ to be connected. The previous build of the firmware tried to communicate with the nRF24L01+ even if it was not connected. This was causing issues on windows. So a build without nRF24L01+ is included.

I'll make it so the nRF24L01+ can be enabled/disabled in the config file later.

Unifying flasher

First version of the unifying flashing script and keyplus hex for nRF24LU1+. Currently the flashing script has only been tested on Linux and must be run manually instead of in the GUI.