qmk/qmk_firmware

[Bug] Introduced in 0.14.0: split kb (elite-c, ergodash) other half not working

Open

#16,273 opened on Feb 8, 2022

View on GitHub
 (3 comments) (0 reactions) (0 assignees)C (43,867 forks)batch import
bughelp wanted

Repository metrics

Stars
 (20,368 stars)
PR merge metrics
 (Avg merge 20d 9h) (27 merged PRs in 30d)

Description

After git pulling the latest qmk my right half wasn't working anymore at all (left is master). I've traced this to version 0.14.0. Latest working version is 0.13.38 with the same json layout file. Compile & flash works fine - qmk clean -a was used everytime.

System Information

  • Keyboard:
    • Revision (if applicable): ergodash/rev1
  • Operating system: PopOS 21.10 (Ubuntu)
  • AVR GCC version: 5.4.0
  • ARM GCC version: (15:9-2019-q4-0ubuntu2) 9.2.1 20191025 (release) [ARM/arm-9-branch revision 277599]
  • QMK Firmware version: 0.14.0 (see above, 0.13.38 works)
  • Any keyboard related software installed?
    • AutoHotKey
    • Karabiner
    • Other:
    • AutoKey

Additional Context

A bit unusual controller setup:

Left half (master): Elite-C Right half: Pro Micro

Contributor guide

Research direction
Investigate the changes between QMK versions 0.13.38 and 0.14.0 related to split keyboard serial communication, particularly in files like serial.c and split common. Check if there were any modifications to handshake or data frame structure that could cause the right half to stop responding.
Tech stack
c
Domain
backend
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitC
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40