* Add Per Key functionality for AutoShift (#11536) * LED Matrix: Reactive effect buffers & advanced indicators (#12588) * [Keyboard] kint36: switch to sym_eager_pk debouncing (#12626) * [Keyboard] kint2pp: reduce input latency by ≈10ms (#12625) * LED Matrix: Split (#12633) * [CI] Format code according to conventions (#12650) * feat: infinite timeout for leader key (#6580) * feat: implement leader_no_timeout logic * docs(leader_key): infinite leader timeout docs * Format code according to conventions (#12680) * Update ADC driver for STM32F1xx, STM32F3xx, STM32F4xx (#12403) * Fix default ADC_RESOLUTION for ADCv3 (and ADCv4) Recent ChibiOS update removed ADC_CFGR1_RES_10BIT from the ADCv3 headers (that macro should not have been there, because ADCv3 has CFGR instead of CFGR1). Fix the default value for ADC_RESOLUTION to use ADC_CFGR_RES_10BITS if it is defined (that name is used for ADCv3 and ADCv4). * Update ADC docs to match the actually used resolution ADC driver for ChibiOS actually uses the 10-bit resolution by default (probably to match AVR); fix the documentation accordingly. Also add both ADC_CFGR_RES_10BITS and ADC_CFGR1_RES_10BIT constants (these names differ according to the ADC implementation in the particular MCU). * Fix pinToMux() for B12 and B13 on STM32F3xx Testing on STM32F303CCT6 revealed that the ADC mux values for B12 and B13 pins were wrong. * Add support for all possible analog pins on STM32F1xx Added ADC mux values for pins A0...A7, B0, B1, C0...C5 on STM32F1xx (they are the same at least for STM32F103x8 and larger F103 devices, and also F102, F105, F107 families). Actually tested on STM32F103C8T6 (therefore pins C0...C5 were not tested). Pins F6...F10, which are present on STM32F103x[C-G] in 144-pin packages, cannot be supported at the moment, because those pins are connected only to ADC3, but the ChibiOS ADC driver for STM32F1xx supports only ADC1. * Add support for all possible analog pins on STM32F4xx Added ADC mux values for pins A0...A7, B0, B1, C0...C5 and optionally F3...F10 (if STM32_ADC_USE_ADC3 is enabled). These mux values are apparently the same for all F4xx devices, except some smaller devices may not have ADC3. Actually tested on STM32F401CCU6, STM32F401CEU6, STM32F411CEU6 (using various WeAct “Blackpill” boards); only pins A0...A7, B0, B1 were tested. Pins F3...F10 are inside `#if STM32_ADC_USE_ADC3` because some devices which don't have ADC3 also don't have the GPIOF port, therefore the code which refers to Fx pins does not compile. * Fix STM32F3xx ADC mux table in documentation The ADC driver documentation had some errors in the mux table for STM32F3xx. Fix this table to match the datasheet and the actual code (mux settings for B12 and B13 were also tested on a real STM32F303CCT6 chip). * Add STM32F1xx ADC pins to the documentation * Add STM32F4xx ADC pins to the documentation * Add initial support for tinyuf2 bootloader (when hosted on F411 blackpill) (#12600) * Add support for jumping to tinyuf2 bootloader. Adds blackpill UF2 example. * Update flashing.md * Update chconf.h * Update config.h * Update halconf.h * Update mcuconf.h * eeprom driver: Refactor where eeprom driver initialisation (and EEPROM emulation initialisation) occurs to make it non-target-specific. (#12671) * Add support for MCU = STM32F446 (#12619) * Add support for MCU = STM32F446 * Update platforms/chibios/GENERIC_STM32_F446XE/configs/config.h * Restore mcuconf.h to the one used by RT-STM32F446RE-NUCLEO64 * stm32f446: update mcuconf.h and board.h for 16MHz operation, with USB enabled, and other peripherals disabled. * Format code according to conventions (#12682) * Format code according to conventions (#12687) * Add STM32L433 and L443 support (#12063) * initial L433 commit * change to XC * fix L433 * disable all peripherals * update system and peripheral clocks * 433 change * use its own board files * revert its own board files * l433 specific change * fix stm32l432xx define * remove duplicate #define * fix bootloader jump * move to L443xx and add i2c2, spi2, usart3 to mcuconf.h * move to L443 * move to L443 * fix sdmmc in mcuconf.h * include STM32L443 * add L443 * Include L443 in compatible microcontrollers * Include L443 in compatible microcontrollers * Update config bootloader jump description * Update ChibiOS define reasoning * Update quantum/mcu_selection.mk * fix git conflict * Updated Function96 with V2 files and removed chconf.h and halconf.h (#12613) * Fix bad PR merge for #6580. (#12721) * Change RGB/LED Matrix to use a simple define for USB suspend (#12697) * [CI] Format code according to conventions (#12731) * Fixing transport's led/rgb matrix suspend state logic (#12770) * [CI] Format code according to conventions (#12772) * Fix comment parsing (#12750) * Added OLED fade out support (#12086) * fix some references to bin/qmk that slipped in (#12832) * Resolve a number of warnings in `qmk generate-api` (#12833) * New command: qmk console (#12828) * stash poc * stash * tidy up implementation * Tidy up slightly for review * Tidy up slightly for review * Bodge environment to make tests pass * Refactor away from asyncio due to windows issues * Filter devices * align vid/pid printing * Add hidapi to the installers * start preparing for multiple hid_listeners * udev rules for hid_listen * refactor to move closer to end state * very basic implementation of the threaded model * refactor how vid/pid/index are supplied and parsed * windows improvements * read the report directly when usage page isn't available * add per-device colors, the choice to show names or numbers, and refactor * add timestamps * Add support for showing bootloaders * tweak the color for bootloaders * Align bootloader disconnect with connect color * add support for showing all bootloaders * fix the pyusb check * tweaks * fix exception * hide a stack trace behind -v * add --no-bootloaders option * add documentation for qmk console * Apply suggestions from code review * pyformat * clean up and flesh out KNOWN_BOOTLOADERS * Remove pointless SERIAL_LINK_ENABLE rules (#12846) * Make Swap Hands use PROGMEM (#12284) This converts the array that the Swap Hands feature uses to use PROGMEM, and to read from that array, as such. Since this array never changes at runtime, there is no reason to keep it in memory. Especially for AVR boards, as memory is a precious resource. * Fix another bin/qmk reference (#12856) * [Keymap] Turn OLED off on suspend in soundmonster keymap (#10419) * Fixup build errors on `develop` branch. (#12723) * LED Matrix: Effects! (#12651) * Fix syntax error when compiling for ARM (#12866) * Remove KEYMAP and LAYOUT_kc (#12160) * alias KEYMAP to LAYOUT * remove KEYMAP and LAYOUT_kc * Add setup, clone, and env to the list of commands we allow even with broken modules (#12868) * Rename `point_t` -> `led_point_t` (#12864) * [Keyboard] updated a vendor name / fixed minor keymap issues (#12881) * Add missing LED Matrix suspend code to suspend.c (#12878) * LED Matrix: Documentation (#12685) * Deprecate `send_unicode_hex_string()` (#12602) * Fix spelling mistake regarding LED Matrix in split_common. (#12888) * [Keymap] Fix QWERTY/DVORAK status output for kzar keymap (#12895) * Use milc.subcommand.config instead of qmk.cli.config (#12915) * Use milc.subcommand.config instead * pyformat * remove the config test * Add function to allow repeated blinking of one layer (#12237) * Implement function rgblight_blink_layer_repeat to allow repeated blinking of one layer at a time * Update doc * Rework rgblight blinking according to requested change * optimize storage * Fixup housekeeping from being invoked twice per loop. (#12933) * matrix: wait for row signal to go HIGH for every row (#12945) I noticed this discrepancy (last row of the matrix treated differently than the others) when optimizing the input latency of my keyboard controller, see also https://michael.stapelberg.ch/posts/2021-05-08-keyboard-input-latency-qmk-kinesis/ Before this commit, when tuning the delays I noticed ghost key presses when pressing the F2 key, which is on the last row of the keyboard matrix: the dead_grave key, which is on the first row of the keyboard matrix, would be incorrectly detected as pressed. After this commit, all keyboard matrix rows are interpreted correctly. I suspect that my setup is more susceptible to this nuance than others because I use GPIO_INPUT_PIN_DELAY=0 and hence don’t have another delay that might mask the problem. * ensure we do not conflict with existing keymap aliases (#12976) * Add support for up to 4 IS31FL3733 drivers (#12342) * Convert Encoder callbacks to be boolean functions (#12805) * [Keyboard] Fix Terrazzo build failure (#12977) * Do not hard set config in CPTC files (#11864) * [Keyboard] Corne - Remove legacy revision support (#12226) * [Keymap] Update to Drashna keymap and user code (based on develop) (#12936) * Add Full-duplex serial driver for ARM boards (#9842) * Document LED_MATRIX_FRAMEBUFFER_EFFECTS (#12987) * Backlight: add defines for default level and breathing state (#12560) * Add dire message about LUFA mass storage bootloader (#13014) * [Keyboard] Remove redundant legacy and common headers for crkbd (#13023) Was causing compiler errors on some systems. * Fix keyboards/keymaps for boolean encoder callback changes (#12985) * `backlight.c`: include `eeprom.h` (#13024) * Add changelog for 2021-05-29 Breaking Changes merge (#12939) * Add ChangeLog for 2021-05-29 Breaking Changes Merge: initial version * Add recent develop changes * Sort recent develop changes * Remove sections for ChibiOS changes per tzarc No ChibiOS changes this round. * Add and sort recent develop changes * add notes about keyboard moves/deletions * import changelog for PR 12172 Documents the change to BOOTMAGIC_ENABLE. * update section headings * re-sort changelog * add additional note regarding Bootmagic changes * remove changelog timestamp * update dates in main Breaking Changes docs * fix broken section anchors in previous changelogs * add link to backlight/eeprom patch to changelog * highlight some more changes * link PRs from section headers * Restore standard readme * run: qmk cformat --core-only
12 KiB
QMK Breaking Change - 2020 Aug 29 Changelog
Four times a year QMK runs a process for merging Breaking Changes. A Breaking Change is any change which modifies how QMK behaves in a way that is incompatible or potentially dangerous. We limit these changes to 4 times per year so that users can have confidence that updating their QMK tree will not break their keymaps.
Changes Requiring User Action :id=changes-requiring-user-action
Relocated Keyboards :id=relocated-keyboards
The Key Company project consolidation (#9547)
relocating boards by flehrad to flehrad/ folder (#9635)
Keyboards released by The Key Company and keyboards designed by flehrad have moved to vendor folders. If you own any of the keyboards listed below, please use the new names to compile your firmware moving forward.
Old Name | New Name |
---|---|
candybar/lefty | tkc/candybar/lefty |
candybar/righty | tkc/candybar/righty |
m0lly | tkc/m0lly |
tkc1800 | tkc/tkc1800 |
bigswitch | flehrad/bigswitch |
handwired/downbubble | flehrad/downbubble |
handwired/numbrero | flehrad/numbrero |
snagpad | flehrad/snagpad |
handwired/tradestation | flehrad/tradestation |
Updated Keyboard Codebases :id=keyboard-updates
Keebio RGB wiring update (#7754)
This pull request changes the configuration for Keebio split boards to use the same RGB strip wiring for each half, which provides the following improvements:
- Easier wiring due to one fewer wire needed (the wire between left DOut to extra data pin) and the fact that wiring is the same for both halves.
- RGB LEDs can be controlled by each half now instead of just master half.
- Extra data line is freed up to allow for I2C usage instead of serial.
If you have customized the value of RGBLED_SPLIT
for your keymap, you will need to undefine it using #undef RGBLED_SPLIT
before defining it to your customized value.
This change affects:
- BFO-9000
- Fourier
- Iris rev2
- Levinson, revs. 1 and 2
- Nyquist, revs. 1 and 2
- Quefrency rev1
- Viterbi, revs. 1 and 2
Changes to Core Functionality :id=core-updates
- Bigger Combo index (#9318)
Allows the Combo feature to support more than 256 combos.
Any fork that uses process_combo_event
needs to update the function's first argument to uint16_t
:
- Old function:
void process_combo_event(uint8_t combo_index, bool pressed)
- New function:
void process_combo_event(uint16_t combo_index, bool pressed)
Core Changes :id=core-changes
Fixes :id=core-fixes
- Mousekeys: scrolling acceleration is no longer coupled to mouse movement acceleration (#9174)
- Keymap Extras: correctly assign Question Mark in Czech layout (#9987)
Additions and Enhancements :id=core-additions
- allow for WS2812 PWM to work on DMAMUX-capable devices (#9471)
- Newer STM32 MCUs have a DMAMUX peripheral, which allows mapping of DMAs to different DMA streams, rather than hard-defining the target streams in silicon.
- Affects STM32L4+ devices, as well as the soon-to-be-supported-by-QMK STM32G4/H7 families.
- Tested on F303/Proton C (ChibiOS v19, non-DMAMUX), G474 (ChibiOS v20, with DMAMUX).
- dual-bank STM32 bootloader support (#8778 and #9738)
- Adds support for STM32 dual-bank flash bootloaders, by toggling a GPIO during early init in order to charge an RC circuit attached to
BOOT0
. - The main rationale behind this is that dual-bank STM32 devices unconditionally execute user-mode code, regardless of whether or not the user-mode code jumps to the bootloader. If either flash bank is valid (and
BOOT0
is low), then the built-in bootloader will skip any sort of DFU. - This PR allows for the initialisation sequencing to charge the RC circuit based on the example circuit posted on Discord, effectively pulling
BOOT0
high before issuing the system reset. As the RC circuit takes a while to discharge, the system reset executes the ROM bootloader which subsequently seesBOOT0
high, and starts executing the DFU routines. - Tested with STM32L082 (with current QMK+current ChibiOS), and STM32G474 (against ChibiOS 20.x).
- Adds support for STM32 dual-bank flash bootloaders, by toggling a GPIO during early init in order to charge an RC circuit attached to
- update Space Cadet and Tap Dance features to use Custom Tapping Term when appropriate (#6259)
- For the Tap Dance feature, this completely removes the need for the
ACTION_TAP_DANCE_FN_ADVANCED_TIME
dance.
- For the Tap Dance feature, this completely removes the need for the
- HID Joystick Interface (#4226 and #9949)
- This implements a joystick feature, including a joystick_task function called from TMK, specific keycodes for joystick buttons and a USB HID interface.
- Tested on V-USB backend and Proton C; compiles but untested on LUFA.
- In order to test, you have to add
JOYSTICK_ENABLE = yes
to yourrules.mk
and
in your config.h.#define JOYSTICK_BUTTON_COUNT 8 #define JOYSTICK_AXES_COUNT 2
- Christmas RGB Underglow animation now fades between green and red (#7648)
RGBLIGHT_EFFECT_CHRISTMAS_INTERVAL
has been greatly decreased; please check your animation if you have customized this value.
- layer state now initializes on startup (#8318)
- This should produce more consistent behavior between the two functions and layer masks.
- added support for HSV->RGB conversion without using CIE curve (#9856)
- added NOEEPROM functions for RGB Matrix (#9487)
- Added eeprom_helpers for toggle, mode, sethsv, speed, similar to rgblight versions.
- Added set_speed function.
- Added helper functions, similar to those in rgblight, in order to add NOEEPROM versions of toggle, step, hue, sat, val, and speed.
- Minor: spelling correction for EEPROM in a debug message.
- flashing firmware using
st-flash
utility from STLink Tools is now supported (#9964) - add ability to dump all makefile variables for the specified target (#8256)
- Adds a new subtarget to builds,
dump_vars
, which allows for printing out all the variables that make knows about, after all substitutions occur. - Example:
make handwired/onekey/proton_c:default:dump_vars
- Adds a new subtarget to builds,
- add ability to change the Auto Shift timeout in real time (#8441)
- added a timer implementation for backlight on ChibiOS (#8291)
- added a third endpoint to V-USB keyboards (#9020)
- added a method to read the OLED display buffer from user space (#8777)
- K-Type refactor (#9864)
- The K-Type has been refactored to use QMK's native matrix scanning routine, and now has partial support for the RGB Matrix feature.
- Joysticks can now be used without defining analog pins (#10169)
Clean-ups and Optimizations :id=core-optimizations
- iWRAP protocol removed (#9284)
- work begun for consolidation of ChibiOS platform files (#8327 and #9315)
- Start of the consolidation work to move the ChibiOS board definitions as well as the default set of configuration files for existing board definitions used by keyboards.
- Uses
/platforms/chibios
as previously discussed on discord. - Consolidates the Proton C configs into the generic F303 definitions.
- Allows for defining a default set of
chconf.h
,halconf.h
, andmcuconf.h
files within the platform definition, which is able to be overridden by the keyboard directly, though include path ordering. - Adds template
chconf.h
,halconf.h
,mcuconf.h
, andboard.h
that can be dropped into a keyboard directory, in order to override rather than replace the entire contents of the respective files. - Removed Proton C QMK board definitions, falling back to ChibiOS board definitions with QMK overrides.
- Uses
- Start of the consolidation work to move the ChibiOS board definitions as well as the default set of configuration files for existing board definitions used by keyboards.
- Various tidy-ups for USB descriptor code (#9005)
- Renamed
keyboard_led_stats
in lufa.c and ChibiOS usb_main.c tokeyboard_led_state
, as well asvusb_keyboard_leds
, for consistency - Formatted CDC and MIDI descriptors better
- Removed
ENDPOINT_CONFIG
macro, it seems pointless and removes the need for endpoint address defines in the middle of the endpoint numbering enum - Fixed (possibly?) V-USB
GET_REPORT
request handling. Not sure about this one, but the existing code appears to always return an empty report - nowsend_keyboard
sets this variable to the current report, matching what the LUFA code does.
- Renamed
- converted
CONSUMER2BLUEFRUIT()
andCONSUMER2RN42()
macros to static inline functions (#9055) - Additional cleanups for V-USB code (#9310)
- Removing the UART stuff entirely, now that we have Console support. Also fixing up various other things; switching some
debug()
calls todprintf()
, movedraw_hid_report
out of the way so that we can implement the shared endpoint stuff.
- Removing the UART stuff entirely, now that we have Console support. Also fixing up various other things; switching some
- removed inclusion of
adafruit_ble.h
fromssd1306.c
(#9355) outputselect.c
is no longer compiled if Bluetooth is disabled (#9356)analogRead()
deprecated in favor ofanalogReadPin()
(#9023)- forcibly disable NKRO on V-USB controllers (#9054)
- removed warning if running backlight on STM32F072 (#10040)
- removed unused CORTEX_VTOR_INIT rules.mk option (#10053)
- improved handling for enabling Link Time Optimization (#9832)
- streamline rules for supporting Kiibohd bootloader (#10129)
- Define
STM32_DMA_REQUIRED
when using DMA-based WS2812 driver on STM32 (#10127) - fix DMA stream ID calculation in ws2812_pwm (#10008)
- remove support for Adafruit EZ Key Bluetooth controller (#10103)