Issues

• Specify how the INTERFACE_HASH digest is derived

  proposal
  harp-tech/protocol#234 · Filter by author glopesdev opened on Sep 17, 2026 · 2.0.0

• Rename the device key to name for consistency with the WhoAmI registry

  proposal
  harp-tech/protocol#230 · Filter by author glopesdev opened on Aug 25, 2026 · 2.0.0

• Clarify R_RESET_DEV defaults and capability-dependent behavior

  proposal
  harp-tech/protocol#226 · Filter by author glopesdev opened on Jun 21, 2026 · 2.0.0
  1

• Device operation conventions for extended-length registers

  proposal
  harp-tech/protocol#221 · Filter by author glopesdev opened on May 11, 2026 · 2.0.0
  2

• Schema for variable-length registers

  proposal
  harp-tech/protocol#220 · Filter by author glopesdev opened on May 11, 2026 · 2.0.0

• Clarify Read request conventions in Device.md

  proposal
  harp-tech/protocol#219 · Filter by author glopesdev opened on May 11, 2026 · 2.0.0

• Add ExtendedLength flag to the binary protocol

  proposal
  harp-tech/protocol#218 · Filter by author glopesdev opened on May 11, 2026 · 2.0.0

• Distribute Harp device GUI applications via .NET tool packages and a unified launcher

  proposal
  harp-tech/protocol#217 · Filter by author glopesdev opened on May 7, 2026
  3

• Consider what an error message to a non-existing register should return

  harp-tech/protocol#216 · Filter by author bruno-f-cruz opened on Apr 29, 2026

• Interface schema does not allow 0-length payloads

  harp-tech/protocol#214 · Filter by author bruno-f-cruz opened on Apr 25, 2026

• Explicitly define the payload field requirements for Read request messages

  harp-tech/protocol#212 · Filter by author bruno-f-cruz opened on Mar 22, 2026
  1

  

• Consider adopting UNIX time epoch

  harp-tech/protocol#206 · Filter by author glopesdev opened on Feb 2, 2026

• Support for new blob message type

  proposal
  harp-tech/protocol#186 · Filter by author glopesdev opened on Nov 2, 2025
  4

• Allow multiple hardware targets in device schema

  proposal
  harp-tech/protocol#172 · Filter by author bruno-f-cruz opened on Oct 6, 2025 · 2.0.0

• Allow specifying write-only and event-only registers

  proposal
  harp-tech/protocol#163 · Filter by author glopesdev opened on Jul 24, 2025 · 2.0.0
  4

• Use a single version number for protocol releases

  proposal
  harp-tech/protocol#148 · Filter by author glopesdev opened on Jun 20, 2025 · 2.0.0
  1

• Consider revising naming of top-level folders

  proposal
  harp-tech/protocol#146 · Filter by author glopesdev opened on Jun 12, 2025 · 2.0.0
  1

• Use a single version number in device repositories

  proposal
  harp-tech/protocol#145 · Filter by author glopesdev opened on Jun 7, 2025 · 2.0.0
  1

• Specification for downsampled clock synchronization protocol

  proposal
  harp-tech/protocol#128 · Filter by author glopesdev opened on Mar 21, 2025 · 2.0.0
  3

• Add compatiblity table between harp hardware core implementations

  harp-tech/protocol#125 · Filter by author bruno-f-cruz opened on Feb 27, 2025
  6

• Add documentation for device.yml specification

  harp-tech/protocol#124 · Filter by author bruno-f-cruz opened on Feb 27, 2025 · 2.0.0
  1

• Define a string interfaceType and establish documentation for well-known types

  proposal
  harp-tech/protocol#118 · Filter by author PathogenDavid opened on Feb 20, 2025 · 2.0.0
  9

• Support variable-length registers in device.yml register specifications

  proposal
  harp-tech/protocol#116 · Filter by author PathogenDavid opened on Feb 20, 2025
  6

• Asynchronous device register programming model

  proposal
  harp-tech/protocol#70 · Filter by author glopesdev opened on Jan 31, 2025

• Add platform architecture to hardware targets in device schema

  proposal
  harp-tech/protocol#66 · Filter by author glopesdev opened on Jan 8, 2025
  1