V500_SOCS lists gk7205v500, gk7205v510 and gk7205v530 in both the CLI (src/defib/protocol/hisilicon_v500.py:32) and the web build (web/protocol.js:138), but none of the three has a profile:
$ ls src/defib/profiles/data/gk7205v5*.json
# nothing
The web UI builds its dropdown from the inline PROFILES object in web/index.html (109 chips) — gk7205v500 is absent, so the chip cannot be selected at all, and the CLI can't resolve it either.
This is live-user-facing: OpenIPC/firmware#1494 has a GK7205V500 (TPTek 5MP) reporter who got in via the vendor bootloader password. Had that failed, the bootrom route we point people to would have had nothing to select.
Either add the three profiles, or drop the SoCs from V500_SOCS so find_protocol fails with a clear "unsupported chip" instead of a missing-profile error.
V500_SOCSlistsgk7205v500,gk7205v510andgk7205v530in both the CLI (src/defib/protocol/hisilicon_v500.py:32) and the web build (web/protocol.js:138), but none of the three has a profile:The web UI builds its dropdown from the inline
PROFILESobject inweb/index.html(109 chips) —gk7205v500is absent, so the chip cannot be selected at all, and the CLI can't resolve it either.This is live-user-facing: OpenIPC/firmware#1494 has a GK7205V500 (TPTek 5MP) reporter who got in via the vendor bootloader password. Had that failed, the bootrom route we point people to would have had nothing to select.
Either add the three profiles, or drop the SoCs from
V500_SOCSsofind_protocolfails with a clear "unsupported chip" instead of a missing-profile error.