September 14 / 2026 · Day 14

Morse Code Practicer

A straight key, ITU timing, live symbols, decode, and selectable speed.

Arduino ESP32 3.3.10 + M5Unified 0.2.19 + M5GFX 0.2.26 + LVGL 9.3.0Prompt contract and reference frame verified; generated hardware candidate awaits hand review
On this page
Illustration of the M5Stack Stopwatch development kit

Used in this project

M5Stack Stopwatch

Stopwatch Dev Kit (ESP32-S3) · C152

1.75″ round AMOLED · 466 × 466 · ESP32-S3

The assignment

Make the left pusher a responsive straight key that teaches Morse timing by feel and sound.

The durable source is this prompt, SPEC.md, the machine-readable contract, and its layered acceptance criteria. Generated firmware is a disposable candidate.

Reference frame

Round-screen acceptance reference for Morse Code Practicer

This is a deterministic screenshot of the visual acceptance model. It defines the intended hierarchy and safe-area use; only a later framebuffer capture from the attached Stopwatch can count as device rendering evidence.

The build prompt

Build ESPtember Day 14: Morse Code Practicer for the M5Stack Stopwatch Dev Kit (C152).

Read these before writing code:
- .agents/skills/build-stopwatch-lessons/SKILL.md
- .agents/skills/prompt-first-embedded-lessons/SKILL.md
- days/day-07-touch-calibration/SPEC.md
- days/day-14-morse-practicer/SPEC.md
- days/day-14-morse-practicer/tests/contract.json

Treat the prompt, spec, tests, and acceptance criteria as source.
Put deterministic behavior in a portable core and keep Arduino, LVGL, M5Unified, storage, network, audio, and sensor adapters outside it.
Run scripts/prompt-contract/validate_day.sh days/day-14-morse-practicer before compiling a device candidate.
Do not edit the contract or tests to make a candidate pass.

Hardware and shared platform

- Target board_M5StopWatch on ESP32-S3 with OPI PSRAM.
- Hold the device with the lanyard loop at the bottom: BtnA is physical left and BtnB is physical right.
- Immediately after M5.begin(), set panel width 468, height 466, offset_x 6, offset_y 0, then rotation 0.
- Never draw rows 466 or 467. Keep focus decoration inset and every interactive bound inside the round safe area.
- Load Preferences namespace espt-touch, blob key record, after display setup and before touch input.
- Accept and validate Day 07 version 1 and version 2 records. Read raw touch, apply the complete shared warp, clamp once, then feed the mapped point to the application.
- Provide the shared runtime calibration entry path. App-only installation must preserve the record.
- Allocate retained frames and large working buffers in PSRAM; fail visibly and over serial when required hardware or memory is unavailable.

Controls

Use a localized control scheme because A straight key must follow press duration directly. BtnA/left: key down up. BtnB/right: clear click speed hold. Short both: cycle speed. Hold both: clear message.
Touch must dispatch the same semantic actions as physical controls.

Lesson behavior

- BtnA starts a 600 Hz sidetone on press and stops it on release without blocking.
- Use PARIS timing: unit_ms = 1200 / WPM; under two units is a dit and two units or more is a dah.
- Decode a letter after a three-unit gap and a word after seven units. Invalid sequences show a question mark.
- BtnB click clears; short both cycles 5, 10, 15, and 20 WPM; hold both clears and returns to 10 WPM.
- Show the current symbol sequence and decoded text without clipping at every speed.

Diagnostics and acceptance

- Prefix serial protocol lines with D14_ and implement status, reset, action, capture, and touchlog commands.
- Report hardware identity, corrected geometry, touch-map version and generation, current portable state, memory headroom, and last named error.
- Injected actions must use the same reducer, hit testing, callbacks, and control recognizer as physical input.
- Retain the exact RGB565 pixels sent to M5GFX and stream captures in bounded chunks without blocking the watchdog.
- Run every scenario in tests/contract.json, generated deterministic sequences, the deliberate mutation, and the lesson-specific checks in SPEC.md.
- Complete 20 largest-state round trips without reset or growing heap/PSRAM use.
- Confirm the active touch-map version and generation remain unchanged.
- Physically review touch alignment, BtnA/BtnB direction, chord behavior, cues, clipping, lower-edge use, and the absence of a black bar.

Record host, compile, injected-device, and physical evidence separately.
Never describe reference rendering or injected input as physical proof.

Required behavior

  • BtnA starts a 600 Hz sidetone on press and stops it on release without blocking.
  • Use PARIS timing: unit_ms = 1200 / WPM; under two units is a dit and two units or more is a dah.
  • Decode a letter after a three-unit gap and a word after seven units. Invalid sequences show a question mark.
  • BtnB click clears; short both cycles 5, 10, 15, and 20 WPM; hold both clears and returns to 10 WPM.
  • Show the current symbol sequence and decoded text without clipping at every speed.

Recorded evidence

The shared contract runner validates Stopwatch geometry, touch-map ownership, control metadata, state types and ranges, deterministic scenarios, round-face control bounds, and 10,000 generated actions against three disposable reducer shapes. A deliberately mutated reducer must fail.

Historical implementation evidence from before the prompt-first Stopwatch migration follows.

Recorded evidence · September 21, 2026: Boot and the decode state machine were verified over serial (D13_STATUS reporting) on the installed firmware. Keying feel at each WPM step awaits a hands-on check, noted in NOTES.md.

The reference screenshot is acceptance-model evidence. The next hardware pass must replace or supplement it with a framebuffer capture and a hand-review record.