ZMK update and Zephyr 3.2 #16

Bumps [loader-utils](https://github.com/webpack/loader-utils) from 2.0.3 to 2.0.4. - [Release notes](https://github.com/webpack/loader-utils/releases) - [Changelog](https://github.com/webpack/loader-utils/blob/v2.0.4/CHANGELOG.md) - [Commits](webpack/loader-utils@v2.0.3...v2.0.4) --- updated-dependencies: - dependency-name: loader-utils dependency-type: indirect ... Signed-off-by: dependabot[bot] <[email protected]>

… features

Added overlays to support building for the nRF5340 development kit. Also added some documentation on how to build and flash ZMK for dual- chip Bluetooth configurations, with an example for the nRF5340.

Co-authored-by: Cem Aksoylar <[email protected]>

* Support underglow, backlight, display, encoder, etc.

- Fixed a stack overflow when enabling Bluetooth. - Increased the I2C buffer size to support displays.

* Add blackbill interconnect metadata. * Add config/overlay for upstream blackpill boards to work with ZMK. * Add pillbug board. * Updated new shield docs. Co-authored-by: Cem Aksoylar <[email protected]>

Same column offset for both transforms, since we use the same pins for both, just apply a different transform. Fixes: 1570

Co-authored-by: Dom H <[email protected]>

Signed-off-by: hyx0329 <[email protected]>

Co-authored-by: Pete Johanson <[email protected]>

Added ZMK_MACRO_DEFAULT_WAIT_MS and ZMK_MACRO_DEFAULT_TAP_MS to set global defaults for the wait-ms and tap-ms properties of macros. Also reduced the default timings for macros, since it's been reported many times that 100 ms is too slow.

Co-authored-by: Pete Johanson <[email protected]>

…etup

* Add to metadata schema for interconnects. * New conventional location for pinout diagrams/pics. * New component to generate the tabs for the new shield doc section on interconnects. * Add XIAO and arduino uno pinout diagram. Co-authored-by: Cem Aksoylar <[email protected]>

Renamed the "Basic Setup" page to "Toolchain Setup" to make it clearer that this is for setting up a development environment for local builds. Linked to the relevant Zephyr setup documentation instead of duplicating that information in our guide. This also switches Windows and macOS setup to using the Zephyr SDK, which is much easier to install. Updated the command for installing Zephyr's Python dependencies to be OS specific, as Windows and macOS don't need the --user flag. Updated the IDE integration page with instructions for determining the compiler path that work with the latest version of the Zephyr SDK.

…iver

Bumps [json5](https://github.com/json5/json5) from 2.2.1 to 2.2.3. - [Release notes](https://github.com/json5/json5/releases) - [Changelog](https://github.com/json5/json5/blob/main/CHANGELOG.md) - [Commits](json5/json5@v2.2.1...v2.2.3) --- updated-dependencies: - dependency-name: json5 dependency-type: indirect ... Signed-off-by: dependabot[bot] <[email protected]>

West has supported a 'name-blocklist' replacement for 'name-blacklist' since v0.9. Signed-off-by: Martí Bolívar <[email protected]>

…rmware#1590) - Asterisk in layer 1 was mapped to 8 - Underscore in layer 1 was mapped to minus - Right GUI in layer 0 was mapped to right Alt - Space in layer 1 was mapped to Return - Plus was mapped with KP_PLUS

Bumps [@sideway/formula](https://github.com/sideway/formula) from 3.0.0 to 3.0.1. - [Release notes](https://github.com/sideway/formula/releases) - [Commits](hapijs/formula@v3.0.0...v3.0.1) --- updated-dependencies: - dependency-name: "@sideway/formula" dependency-type: indirect ... Signed-off-by: dependabot[bot] <[email protected]>

Bumps [http-cache-semantics](https://github.com/kornelski/http-cache-semantics) from 4.1.0 to 4.1.1. - [Release notes](https://github.com/kornelski/http-cache-semantics/releases) - [Commits](kornelski/http-cache-semantics@v4.1.0...v4.1.1) --- updated-dependencies: - dependency-name: http-cache-semantics dependency-type: indirect ... Signed-off-by: dependabot[bot] <[email protected]>

The default configuration for corneish-zen enables a USB CDC endpoint by default. This is most probably a debugging left-over. Disable that endpoint. CONFIG_ZMK_USB_LOGGING depends on it anyway, so it will be enabled again with that config option set.

* Ferris board's CDC ACM node was accidentally nested under the wrong node, causing USB logging builds to fail with cryptic error.

* LV_ prefix from new LVGL official Kconfig now used. * API changes for themes, container object removal, etc. * Add our own Kconfig and code for theme default small font. * Remove some hardcoded sizes.

* Upstream now has a node w/ label `reset` on many boards, so renaming our reset behavior node label to `sys_reset`.

* Zephyr moved to properly namespaced headers, so major "rip the bandaid" commit to move us to those everywhere.

* Move away from DT_LABEL. * Move to DEVICE_DT_GET for non-behavior device access. * Move various drivers to `gpio_spec_dt` and `DT` related macros. * Remove mcp23017 while at it, since better upstream driver is available.

Baseline config and overlay for the following: * `rpi_pico` * `adafruit_kb2040` * `sparkfun_pro_micro_rp2040` * `adafruit_qt_py_rp2040` * `seeeduino_xiao_rp2040` * `boardsource_blok` * `01space_rp2040_042lcd` Co-authored-by: Joel Spadin <[email protected]>

When enabling our high level USB logging, disable the USB driver logging itself entirely, to avoid logging in the driver causing errors when USB isn't up yet to send the logs.

Co-authored-by: Cem Aksoylar <[email protected]>

Ensure we only clear the display when turning blanking off the first time, not every time, to avoid duplicate clears.

Co-authored-by: Cem Aksoylar <[email protected]>

`pinctrl-0` setting missing `<>`.

* Workaround Zephyr bug for Nordic SPI(M) driver after the pinctrl refactor by using spi3 peripheral for the SPI bus for the WS2812 led_strip driver.

Fixed an issue where the sticky key behavior would call ZMK_EVENT_RAISE_AFTER(), which would free the provided event, but then it would keep using that now-freed event data.

Duplicate the existing tests with `quick-release` enabled: - 8-lsk-osk-combination-quick-release - 10-callum-mods-quick-release

Before this change, if a matrix position was not present in the transform, various incorrect behaviors would happen: 1) In some cases out-of-bounds accesses: Note that the size of the`transform[]` array does not necessarily match the size of the matrix. So for example if key position (ZMK_MATRIX_COLS-1, ZMK_MATRIX_ROWS-1) is not present in the transform, but ends up being pressed, then the array will be accessed beyond its size, and any data could be returned. 2) In other cases the 0th position in the keymap will be used because the `transform[]` array is initialized to all zeros.

* Clarify the potential need of adding the ignore-modifiers setting for new sticky key behaviors. * Add ignore-modifiers setting to skq example * Update docs/docs/behaviors/sticky-key.md Co-authored-by: Cem Aksoylar <[email protected]>

Extended the virtual key position system from combos so that each sensor also gets a virtual key position. This allows sensor behaviors to use the behavior queue API.

* Move to SPI3 for underglow peripheral, needed after the move to pinctrl.

* Add new sensor behaviors that either take full bindings add definition, or accept parameters when bound in the keymap. * Remove existing hard-coded key press sensor behavior and instead leverage new generic sensor behaviors to achieve the same functionality. Co-authored-by: [email protected]

* Remove TAPPING_FORCE_HOLD reference * Remove IGNORE_MOD_TAP_INTERRUPT reference

Updated existing pre-commit hooks and added some new hooks: - Remove trailing whitespace - Ensure every non-empty file ends with a new line - Check YAML file validity - Prevent adding large files - Ensure any scripts with shebangs are executable Added a GitHub action to run pre-commit on every commit. Removed any existing actions which duplicate pre-commit. Ran pre-commit on the codebase.

Standardized indentation to use spaces with a new pre-commit hook.

Added a workaround to select the latest version of Prettier with pre-commit, since the pre-commit mirror repo started tracking alpha releases and doesn't have anything beyond 2.7.1.

* Reports of constant/frequent disconnects, with HCI err 0x28, "instant passed", seem linked to newer LLCP that became default in Zephyr 3.2, so revert to the Legacy LLCP for now until a proper fix for new LLCP can be found.

Adds support for the CKP family of boards BT60V2 ANSIHotswap, ISO Hotswap, ANSI Lowpro and soldered BT65 ANSI Hotswap, ISO Hotswap and soldered BT75 ANSI Hotswap and soldered The BT65 and BT75 are stylised as btXX_v1 in order to maintain compatibility with customers existing zmk-config setups in the same way the BT60 V1 was handled when merged into main. CKP boards have identical pinmapping between hotswap and soldered so there's only one set of defconfig, dts, keymap, yaml and yml files per size

Added a key property to interconnect tabs list items to fix a React warning.

…node

In split_central_update_indicators_callback, it seems that the peripheral is sometimes considered connected before the GATT characteristics have been discovered. If this is the case, the update_hid_indicators handle will not yet be set, and must not be written to.

Not after the last output

As a counterpart to zmk_battery_state_of_charge()

Based on PR#1140 with several changes as described in this comment: zmkfirmware#1140 (comment) * Minimize the api changes for bluetooth by keeping zmk_hid_get_keyboard_report() and returning the .body like before. * Keeping the logic about "full" vs "body" entirely within the usb code path. * The endpoint now calls either zmk_usb_hid_send_keyboard_report() and zmk_usb_hid_send_consumer_report() instead of zmk_usb_hid_send_report(...). - These functions now internally dispatch on protocol to either zmk_hid_get_keyboard_report() or a new function for boot reports zmk_hid_get_boot_report(). - There's a change here from the PR version in the behavior of get_report(): when in boot protocol, don't include the report id. I believe this is correct, in that implicit boot protocol report descriptor does not use multiple reports, so any boot protocol report should not include the report id field. * Use a single definition of a boot report, used for regular reports in non-6KRO, and for rollover in all branches. * Handle gaps in the zmk report when producing a boot report in HKRO mode. For .example, if it was 8KRO, it would be possible to have the state 0 0 0 0 0 0 0 17 (by pressing 8 keys, and letting go of the first 7). Copying the first 6 bytes would not show up the single pressed key.

SOF events were introduced by the boot protocol changes, and required internally by Zephyr's idle support, but are unused within ZMK itself. Ignore them in the usb status callback.

Adds Glove80's status indicator using RGB underglow support. Requires ZMK PR#999 and PR#1243. The underglow status is able to show layer state, battery levels, caps/num/scroll-lock, BLE and USB state. The underglow positions selected for each of these indicators is configured using the new devicetree node zmk,underglow-indicators, which takes an array of integer LED positions for each feature.

Disable underglow when battery below 10%, halve brightness when battery below 20%

Adds a Kconfig setting for the default EXT_POWER status at initialization time. Previously it was always initialized to on if no saved value was present.

Provides an entry point that builds and returns a combined LH + RH keyboard firmware when provided a keymap via a POST body. Wraps compilation with ccache, and includes a pre-warmed cache of the build in /tmp/ccache. To maximize chance of a direct cache hit, changes the lambda driver to always build in /tmp/build. some back of the envelope measurements (2012 xeon e3-1230v2, nixos) clean build, no cache -> 21.308 clean build, cache -> 7.145 modified keymap, clean build, cache -> 12.127

…script

From 621d946. This patch can be dropped on the next rebase to upstream.

ZMK update and Zephyr 3.2 #16

ZMK update and Zephyr 3.2 #16

Commits on Sep 16, 2022

Commits on Nov 26, 2022

Commits on Dec 1, 2022

Commits on Dec 8, 2022

Commits on Dec 10, 2022

Commits on Dec 11, 2022

Commits on Dec 14, 2022

Commits on Dec 16, 2022

Commits on Dec 17, 2022

Commits on Dec 18, 2022

Commits on Dec 20, 2022

Commits on Dec 21, 2022

Commits on Dec 23, 2022

Commits on Jan 5, 2023

Commits on Jan 7, 2023

Commits on Jan 18, 2023

Commits on Jan 20, 2023

Commits on Jan 27, 2023

Commits on Feb 1, 2023

Commits on Feb 3, 2023

Commits on Feb 8, 2023

Commits on Feb 22, 2023

Commits on Feb 25, 2023

Commits on Mar 12, 2023

Commits on Mar 22, 2023

Commits on Mar 25, 2023

Commits on Apr 6, 2023

Commits on Apr 7, 2023

Commits on Apr 8, 2023

Commits on Apr 9, 2023

Commits on Apr 10, 2023

Commits on Apr 12, 2023

Commits on Apr 14, 2023

Commits on Apr 16, 2023

Commits on Apr 17, 2023

Commits on Apr 18, 2023

Commits on Apr 21, 2023

Commits on Apr 22, 2023

Commits on Apr 23, 2023

Commits on Apr 24, 2023

Commits on Apr 25, 2023

Commits on Apr 26, 2023

Commits on May 4, 2023

Commits on Jun 27, 2023

Commits on Jun 28, 2023

Commits on Jul 8, 2023