From a237bd92c66b40e13b14a596cee888572e0143d0 Mon Sep 17 00:00:00 2001 From: QIU SHENGMING Date: Thu, 1 Oct 2026 16:12:36 +0800 Subject: [PATCH] Stop teaching the old address flags in the docs The flags are optional now and the page needs no addresses at all, so the examples no longer paste one build's numbers: screenshot.py is shown asking the firmware through tools/uvk5_buffers.py, and the webui example omits them entirely. The paragraph that said they default to one known build is replaced with what actually happens. --- README.md | 8 +++++--- README.zh-CN.md | 6 ++++-- tools/webui.py | 2 +- 3 files changed, 10 insertions(+), 6 deletions(-) diff --git a/README.md b/README.md index 052dc9a..79bf31c 100644 --- a/README.md +++ b/README.md @@ -184,9 +184,11 @@ Five minutes from a checkout to a running radio on a web page. python3 tools/webui.py --qemu ~/src/qemu-7.2/build/qemu-system-arm \ --elf assets/firmware/f4hwn.fieldops.v6.0.0.bin # then open http://127.0.0.1:8080/ -`--frame-addr` and `--status-addr` default to one known build and move between builds; -see [Web remote control](#web-remote-control) for how to find them. On Windows, -`work/run-webui.ps1` wraps step 4 with this machine's paths. +`--frame-addr` and `--status-addr` are optional, and normally omitted. The page draws the +**display controller's own memory**, which is the screen for every firmware and needs no +addresses at all; those two only serve the guest-RAM fallback, and `tools/uvk5_buffers.py` +finds them in whatever firmware is running (`--frame-addr` on the command line skips the +search). Nothing in this repository holds a build's addresses. Drop any `.bin` on the page to boot it. The page's **Firmware slots** table reads and writes the multi-system firmware's four slots in the flash image, and **Multiboot** diff --git a/README.zh-CN.md b/README.zh-CN.md index e0654c2..bfc8f91 100644 --- a/README.zh-CN.md +++ b/README.zh-CN.md @@ -162,8 +162,10 @@ uvk5_elf.sh 探针脚本从哪里找固件（环境变量，然后本 python3 tools/webui.py --qemu ~/src/qemu-7.2/build/qemu-system-arm \ --elf assets/firmware/f4hwn.fieldops.v6.0.0.bin # 然后打开 http://127.0.0.1:8080/ -`--frame-addr` 与 `--status-addr` 默认值对应一份已知构建，换构建会变——怎么找见 -[网页远控](#网页远控)。Windows 上 `work/run-webui.ps1` 把第 4 步按本机路径包好了。 +`--frame-addr` 与 `--status-addr` 都是可选的，通常不传。页面画的是**显示控制器自己的显存** —— +对任何固件那就是屏幕，不需要任何地址；这两个参数只服务 guest RAM 回落路径，而 +`tools/uvk5_buffers.py` 会从**正在运行的那份固件**里把它们找出来（命令行给了 `--frame-addr` +就跳过搜索）。仓库里不保存任何一份构建的地址。 把任意 `.bin` 拖到页面上即可启动。页面上的 **Firmware slots** 表可以读写 flash 镜像里 多系统固件的四个槽位，**Multiboot** 会按住 MENU 重启以进入多系统菜单——前提是那份构建 diff --git a/tools/webui.py b/tools/webui.py index e01b3d7..ef1f9f7 100644 --- a/tools/webui.py +++ b/tools/webui.py @@ -6,7 +6,7 @@ so the emulated radio can be driven from a browser. Start the emulator first (tools/run.sh), then: - python3 tools/webui.py --frame-addr 0x200013DC --status-addr 0x2000175C + python3 tools/webui.py # no addresses: the page draws the panel's own memory Then open http://127.0.0.1:8080/