ht9045-v899

Analyzes HT9045 V3.33.899.0 firmware code, alarms, and InArm state machines.

Updated May 28, 2026
One-click install
npx skills add https://github.com/HPI-Jimmy-Chiu/HT904_V899 --skill ht9045-v899-hpi-jimmy-chiu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ht9045-v899
Source: https://github.com/HPI-Jimmy-Chiu/HT904_V899/tree/main/.agents/skills/ht9045-v899
Command: npx skills add https://github.com/HPI-Jimmy-Chiu/HT904_V899 --skill ht9045-v899-hpi-jimmy-chiu

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Engineers working on the HT9045 V3.33.899.0 handler firmware need to locate alarms, trace HotPlate Data Swap errors, and compare version differences across a large C/C++ codebase without manually searching thousands of lines. ## Core Features & Use Cases - Alarm and Error Analysis: Trace HotPlate Data Swap errors in DoPlaceToHPSwapData, including duplicate-placement conflicts and NULL_IC data inconsistency conditions with exact file and line references. - State Machine Navigation: Follow the iArmTask state machine for the 2x4-16 InArm configuration and the iInArmType dispatch table covering 27 site variants. - Version Knowledge Base: Access compile flags, module indexes, customer code branches (AMKOR, Qualcomm, HiSilicon), and shared parameter checkpoints such as ATC.ini and Mot_Table.csv. - Use Case: When a HotPlate Data Swap error occurs on a 16-site line, ask the Skill to identify the trigger condition, the responsible function in ainarm_SearchPlacePlate.cpp, and the relevant debug hook flags. ## Quick Start Ask the Skill to analyze a HotPlate Data Swap error on the V899 build and identify the root cause function and trigger conditions.

Frequently Asked Questions about ht9045-v899

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I troubleshoot a HotPlate Data Swap error on HT9045?▼

HotPlate Data Swap errors originate in DoPlaceToHPSwapData in ainarm_SearchPlacePlate.cpp around lines 4615-4690. Error 1 indicates a duplicate placement conflict where both the HotPlate slot and InArm hold an IC, while Error 2 indicates the InArm carries a NULL_IC into an occupied slot.

How does the iInArmType dispatch table work in V899 firmware?▼

The InArm main dispatcher in ainarm9045.cpp (lines 1502-1588) routes execution based on the iInArmType enum to one of 27 site-configuration functions such as DoInArm_9045_2x4_16. Each variant maps to a dedicated source file with its own row, column, and sucker configuration.

What is the iArmTask state machine flow for the 2x4-16 configuration?▼

The DoInArm_9045_2x4_16 state machine starts at case 1 (move to wait position), routes through case 10 decision logic, picks from the loader at case 100, places to HotPlate at case 1100, picks from HotPlate at case 1500, and places to Shuttle at case 2000.

Which compile flags are enabled in HT9045 V3.33.899.0?▼

Enabled flags include ALIAS set to HT9045, ATC_HEAD_COUNT 32, INDEX_HEAT_COUNT 32, USE_CompareCommandPos, DEBUG_SOFTWARE_EXEC_TIME, ATC_SW_VER 1031, and ATC_FW_VER 1032. SOFT_SIMULTE and DEBUG_OneCycleHotPlate are disabled by default.

Does customer code affect HotPlate Data Swap checking behavior?▼

Yes, the CUSTOMER_CODE value in MachineType.h controls flow branches. CC_AMKOR_China and CC_QUALCOMM enable HotPlate Data Swap checks in QA and offline modes, while HiSilicon, Nvidia, and TSMC have their own dedicated process branches.

What tasks are outside the scope of this V899 analysis skill?▼

Weekly reports, case status tracking, release notes, and installation package records are handled by the Weekly_AI agent, not this Skill. Formal deliverables belong under the Customer/<client>/<CASE>/04_release/ path and require a handoff with root cause, fixed files, and validation results.