HSIMCHUMAN–AI REALITY INFRASTRUCTURE
Reality R&D / T736 / Continue Evidence / C0-009

C0-009 · FIRST SUPPLIER BOARD EVALUATION · 2026-10-11 · EXPERIMENTAL

The computing route works. Unattended restart is not yet proven. T736 第一次供应商产品研究结论:计算路线可行,自动开机恢复尚未就绪。

This is a bounded evaluation of one Allwinner T736 Ubuntu evaluation board (AIS-equipped Board B / hk2)—not a production launch or certification of an entire supplier product family. Pinned NPU hardware binaries actually computed; authenticated on-demand MCP could invoke two fixed NPU operations. A later real reboot exposed a separate startup failure. 这是一台实验设备的实际验证,不是生产级产品验收。 我们已证明固定 NPU 推理及受限 MCP 调用真实可行,也通过一次真实 reboot 发现 启动恢复与 WD 外接磁盘的时序问题。成功与失败都是研究证据。

HARDWARE FEASIBILITY · DEMONSTRATED BOUNDED MCP NPU · 6+6 ON PRIOR BOOT AUTO NPU RESTART · FAILED PRODUCTION READINESS · NOT CLAIMED
6 + 6Independent MCP Tools + Resources · previous boot
256 BExact supplier custom_lut Golden · previous boot
1Real authorized reboot · automatic NPU recovery failed
SafeFailed service disabled; WD normally unmounted
Research conclusion / 研究判断: Continue small-scale engineering R&D; do not claim an unattended, production-ready edge server. Single-sample reported NPU times are not general-purpose AI accuracy, end-to-end API latency, throughput or availability measurements. 适合下一阶段工程研发与复制验证;不能宣称已达到生产级 无人值守重启、通用模型精度、完整硬盘保护或长期运营商网络 SLA。

EVIDENCE FIRST · ACTUAL SUCCESSFUL LAB TESTS

What the experimental board did prove 实机证明了什么

01 · NPU physical execution A pinned vipcore driver bound to real hardware; fixed NBG inference ran. Its output accuracy was not separately Golden-verified. 实际加载 NPU 内核模块,固定 NBG 样本运行成功; 该 NBG 未进行独立 Golden 准确率检验。
02 · Supplier numerical reference A separate vendor custom_lut sample passed an exact 256-byte Golden comparison. 另一个原厂 custom_lut 样本与 256 字节参考输出精确一致。
03 · On-demand MCP control Independent official MCP Client listed 6 Tools and 6 Resources, invoked both fixed NPU operations and matched their result resource receipts. 独立客户端真正通过 MCP 调用固定 NPU 与 Golden, 并回读关联 operation、日志及 SHA256 证据。
04 · Other local capabilities Scoped LTE PPP connectivity and routed egress were observed after a single ModemManager recovery; WD VFAT and exFAT supported read-only metadata mounts and normal unmount. 蜂窝网络曾实测恢复出口;WD 两个分区也分别通过 只读挂载、文件系统容量元数据读取及正常卸载。

Historical acceptance: C0-008 · Independent NPU & Golden evidence. This was successful on a previous boot, not the current rebooted hardware state.

NEGATIVE REBOOT EVIDENCE · B0-009R1

What the real reboot revealed 真实重启揭示的产品集成缺口

The T736 resumed Linux, authenticated Ethernet SSH, its original read-only MCP 3 Tools + 3 Resources, and cellular ppp0. However, its NPU boot restore unit failed early, before critical peripheral enumeration finished, and /dev/vipcore remained absent. No new-boot NPU / Golden / 6+6 claim was accepted.

The external WD drive subsequently appeared and both partitions were automatically mounted rw. The kernel reported unclean-unmount warnings for VFAT and exFAT; this is a warning, not proof of user-file corruption. The exact first unavailable boot prerequisite was not isolated by the original loader's generic error message. Linux、Mac 有线 SSH、原 MCP 3×3 及蜂窝 PPP 恢复; 但 NPU 自动加载服务在硬件就绪前失败,新的 Boot ID 上没有 NPU/G1 验收。 WD 在开机后自动读写挂载并出现未正确卸载提示,不能推断实际数据损坏, 也不能忽略启动顺序和存储安全问题。

Recovery after the experiment: the failed NPU startup unit was disabled; WD was synced and both partitions normally unmounted without forcing, repair or formatting. A separate live SSH readback confirmed the rollback. No second reboot was attempted.

WHAT THIS MEANS FOR PRODUCT R&D

Research feasibility is not product readiness 把供应商样板转成有依据的下一步工程判断

Continue: evaluate the T736 as a GenAI-native, local, MCP-addressable compute reference. Reuse the verified source hashes, fixed examples, hardware operation evidence and observed failure conditions.

Hold: unattended boot, WD automount policy, filesystem health, new-boot NPU / MCP 6+6, general model coverage and any production-readiness or broad supplier capability promises. Future changes require separate testing and acceptance.

继续研究 T736 作为 Ubuntu 本地 MCP 计算节点的可能性; 下一阶段优先处理启动时序、外设就绪、WD 安全及新 Boot 独立验收。 不要以一次实验装机成功替代产品认证,也不把其他供应商产品视为已测试。