Files
uv-k5-v3-emulator/harness/sim_keyer.h
mckero c0a09827ed UV-K5 V3 emulator: QEMU machine for the PY32F071
Adds a QEMU machine for the Puya PY32F071 (Cortex-M0+) so Quansheng UV-K5 V3
firmware can run on a PC. The firmware boots to its main loop in about five
seconds and the LCD contents are readable.

Register layouts come from the vendor CMSIS header shipped with the firmware
rather than guesswork. Modelled: RCC, GPIO, ADC, both SPI controllers, DMA1 and
the PY25Q16 flash; everything else answers through a logging catch-all, which is
how the next thing worth modelling gets identified.

Seven things had to be right before it would boot, each found by watching where
the firmware stopped: flash aliased at the application offset, clock ready bits,
self-clearing ADC calibration, SPI transfer flags, DMA-driven flash reads,
SysTick poll acceleration, and the bit-banged transceiver bus idling low.

SysTick needs explanation. SYSTICK_DelayUs polls the counter and accumulates
differences; under emulation a register read costs far more relative to guest
time, so a measured 120 ms delay would have taken about 7.7 hours. Lowering the
clock does not help because the bottleneck is loop iterations, not counter speed.
Reporting a value that runs ahead of the real counter does, via a new poll-boost
property on SysTick. Guest time therefore runs fast during delays: fine for
exercising menus and control flow, wrong for judging signal timing.

Also includes the host build of the CW timing chain (harness, stubs, shim,
tests), which compiles app/cwkeyer.c and app/cwmacro.c unmodified against stub
drivers with a virtual clock and scripted paddle input.

Known gap: keypad rows reach the firmware's scan and KEYBOARD_Poll returns the
right key code, but the UI does not react yet.

Not modelled, and not intended to be: radio behaviour. The transceiver chip has
no public datasheet, so keying envelopes and emissions need real hardware.
2026-08-27 14:59:21 +01:00

28 lines
987 B
C

/* Test-facing driver for the CW keyer.
*
* Wraps the firmware's CW_HandleState() in the polling loop the real main loop
* provides, and translates its returned action into recorded carrier events.
* A scenario is: configure, script a paddle timeline, run, assert.
*/
#ifndef SIM_KEYER_H
#define SIM_KEYER_H
#include <stdbool.h>
#include <stdint.h>
// Resets clock, paddle script, recorder, keyer state and EEPROM, then applies
// the given configuration. `key_input` is a CW_KEY_INPUT_* bitmap value (see
// settings.h); `keyer_mode` is a CW_IambicMode_t.
void SIM_KeyerBegin(uint8_t key_input, uint8_t keyer_mode, uint8_t wpm);
// Runs the polling loop for the whole queued paddle timeline, plus `tail_ms` of
// idle time so trailing character/word gaps can be detected.
void SIM_KeyerRun(uint32_t tail_ms);
// One dit at the configured speed, in milliseconds. The reference for asserting
// element durations: a dah is three of these.
uint32_t SIM_KeyerDitMs(void);
#endif