Skip to content

fix(windows): include required WCHISP verification mode key - #67

Open
yomoe wants to merge 1 commit into
AhakeyAI:eternal-devfrom
yomoe:fix/windows-wchisp-config
Open

yomoe wants to merge 1 commit into
AhakeyAI:eternal-devfrom
yomoe:fix/windows-wchisp-config

Conversation

@yomoe

@yomoe yomoe commented Sep 19, 2026

Copy link
Copy Markdown

WCHISP 4.0 rejects the generated CH57x/CH58x INI with vendor Code 2 (Fail to get parameters from cfg file) before programming when the literal Quick Verification Mode key is missing.

Emit Quick Verification Mode=0 in [CH57x-58xUICfg] and assert its presence in WchIspConfigTest. DataFlash preservation, reset/protection settings, ordinary verification and terminal-result handling are unchanged.

Validation:

  • Independent JDK 17 checkout: mvn -f ahakeyconfig-win-java/pom.xml -Dtest=WchIspConfigTest,OfficialWchIspAdapterTest,FirmwareUpdateServiceTest,WchIspResultParserTest package — 39 tests passed; release contents OK.
  • Read-only INI comparison: the original configuration returned Code 2; adding only this field reached discovery (Code 5 with no ISP device).
  • Earlier explicitly authorized official v1.1.0 hardware update: download and independent verification both completed at 100% with vendor Code=0 / Succeed.

The hardware result validates this configuration fix, not compatibility with the development firmware contract: the device still returned legacy 1.0 status bytes and lacked the expected newer command payloads. No firmware images, proprietary tools or runtime logs are included.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants