refactor(logging): remove remote logging subsystem

2026-10-08 16:08:41 +08:00
parent 5d849033c3
commit 3160a33f50
22 changed files with 12 additions and 2546 deletions
@@ -1,5 +1,7 @@
 # Flash 与内存容量分析、风险及后续开发建议

+> 历史容量快照：文中远程日志与 `logfs` 已从当前固件移除，分区地址和容量应以现行 `16m.csv` 与最新构建产物为准。
+
 本文记录当前固件的 Flash 分区使用情况、静态 RAM 使用情况、运行时内存风险、可优化内容和后续开发约束，用于功能评审、资源接入、OTA 设计和长期容量管理。

 LittleFS 资源从源码到设备的详细流程见：
@@ -1,5 +1,7 @@
 # OTA 后首次语音启动与后台上传隔离修复说明

+> 历史实现记录：文中远程日志及 LogFS 上传路径已从当前固件移除，相关描述不代表现行行为。
+
 ## 1. 提交信息

 ```text
@@ -414,4 +416,3 @@ Listening 到达时间
 4. 模拟服务端 task 启动超过 10 秒，确认出现 `Local wake timed-out task cleanup`，下一次唤醒创建新 task。
 5. 在 ASR 结束到 TTS 开始期间观察远程日志，确认没有启动后台 HTTPS 上传。
 6. 开机 60 秒后保持语音空闲，确认历史日志和 coredump 能继续上传，而不是永久被阻塞。
-
@@ -14,7 +14,7 @@
 - Wi-Fi 连接、重连和配置热点；
 - 设备身份、JWT 和会话令牌；
 - 用户出生资料、每日运势和财富方向；
- NVS、LittleFS、远程日志和工厂 CLI。
+- NVS、LittleFS 和工厂 CLI。

 ## 2. 分层架构

@@ -269,7 +269,6 @@ flowchart TB
    LCD["cp_lcd_render<br/>LCD 启动"]
    Events["cp_system_event<br/>事件分发"]
    Keys["cp_key_input<br/>GPIO 与消抖"]
-    Logs["remote log worker"]
    Fortune["cp_fortune<br/>每日运势"]
    Monitor["cp_task_monitor<br/>可选诊断"]

@@ -278,7 +277,6 @@ flowchart TB
    Start --> LCD
    Start --> Events
    Start --> Keys
-    Start --> Logs
    Start --> Fortune
    Start --> Monitor
 ```
@@ -705,4 +703,3 @@ control_plane_stop_runtime_workers()
 - `components/platform/src/multimodal/transport_ws/transport_ws_runtime_impl.c`
 - `components/platform/src/lcd_direct.c`
 - `components/platform/src/platform_stepper_driver.c`
-
@@ -107,7 +107,7 @@ When enabled, the first multimodal HTTPS connection failure requests controlled

 When disabled, HTTPS and WebSocket retry behavior remains active, but the firmware does not intentionally disconnect a Wi-Fi connection that is still reported as associated.

-Runtime impact when enabled: all device network traffic is interrupted during reassociation, including WebSocket, HTTPS, remote logging, LAN HTTP, and mDNS traffic. It is enabled by default because field testing demonstrated a stale STA data path that repeated transport-level reconnects could not recover. Disable it only when deliberate reassociation is unacceptable for a deployment.
+Runtime impact when enabled: all device network traffic is interrupted during reassociation, including WebSocket, HTTPS, LAN HTTP, and mDNS traffic. It is enabled by default because field testing demonstrated a stale STA data path that repeated transport-level reconnects could not recover. Disable it only when deliberate reassociation is unacceptable for a deployment.

 The HTTPS preflight performs one application-level DNS lookup. lwIP already
 retransmits DNS queries internally, and the captured failure took about 14