mirror of
https://github.com/MCKero6423/uv-k5-v3-emulator.git
synced 2026-10-02 11:07:31 +00:00
mckero
c0a09827ed
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.
60 lines
1.6 KiB
Bash
Executable File
60 lines
1.6 KiB
Bash
Executable File
#!/usr/bin/env bash
|
|
# What does KEYBOARD_Poll return, and what does the app do with it?
|
|
#
|
|
# The scan is already proven to read the right row (IDR bit 15 low for MENU), so
|
|
# the remaining question is downstream: does Poll return the key code, and does
|
|
# the debounce in app.c accept it?
|
|
set -uo pipefail
|
|
|
|
ELF="${ELF:-$HOME/uvk5-port/uvk5-sat/build/CW/nr7y.cw.elf}"
|
|
KEY="${1:-MENU}"
|
|
|
|
python3 - "$KEY" <<'PY'
|
|
import json, socket, sys
|
|
s = socket.socket(socket.AF_UNIX, socket.SOCK_STREAM)
|
|
s.connect("/tmp/uvk5-qmp.sock")
|
|
buf = b""
|
|
|
|
|
|
def rd():
|
|
global buf
|
|
while b"\n" not in buf:
|
|
buf += s.recv(4096)
|
|
line, buf = buf.split(b"\n", 1)
|
|
return json.loads(line)
|
|
|
|
|
|
rd()
|
|
for p in ({"execute": "qmp_capabilities"},
|
|
{"execute": "qom-set",
|
|
"arguments": {"path": "/machine/keypad", "property": "press",
|
|
"value": sys.argv[1]}}):
|
|
s.sendall(json.dumps(p).encode() + b"\n")
|
|
while True:
|
|
m = rd()
|
|
if "return" in m or "error" in m:
|
|
break
|
|
print(f"holding {sys.argv[1]}")
|
|
PY
|
|
|
|
SCRIPT=$(mktemp --suffix=.gdb)
|
|
trap 'rm -f "$SCRIPT"' EXIT
|
|
|
|
{
|
|
echo "set confirm off"
|
|
echo "set pagination off"
|
|
echo "target remote :1234"
|
|
# Return value in r0. KEY_MENU is 5 in KEY_Code_t; KEY_INVALID is 255.
|
|
echo "break *0x08004c58"
|
|
echo "commands"
|
|
echo "silent"
|
|
echo "printf \"Poll returns %d\\n\", \$r0"
|
|
echo "continue"
|
|
echo "end"
|
|
for _ in $(seq 8); do echo "continue"; done
|
|
echo "detach"
|
|
echo "quit"
|
|
} >"$SCRIPT"
|
|
|
|
timeout 90 gdb-multiarch -batch -x "$SCRIPT" "$ELF" 2>/dev/null | grep 'Poll returns' | head -8
|