Parse customer hardware pin requirement Excel documents into structured JSON for Tai-Action MCU series. Covers installation, parsing workflow, output schema, and troubleshooting for all supported subsystems.
Parse non-standardized hardware pin requirement Excel files into strongly-typed validated JSON for Tai-Action MCU series.
Activate this Skill when ANY of the following conditions are detected:
1. Explicit — User mentions pin requirement Excel parsing
2. File Context — Pin requirement Excel detected
.xlsx files containing columns: 芯片型号, 模块, 引脚功能, IO索引prd/ or requirements directories with pin mapping datatae_pinmap_parser.py3. Problem Context — Parsing issues
All Tai-Action MCU series chips (TAE32G58XX etc.) when customer requirements are provided as structured Excel documents.
python tools/tae_pinmap_parser.py input.xlsx # Output to ./input.json
python tools/tae_pinmap_parser.py input.xlsx /tmp # Output to /tmp/input.json
python tools/tae_pinmap_parser.py input.xlsx /tmp -o out.json # Output to /tmp/out.json
python tools/tae_pinmap_parser.py input.xlsx --no-images # Skip image extraction
| Category | Module Keys | Output Field | Config Model |
|---|---|---|---|
| ADC | ADC | Sensing_ADC | ADCConfig |
| HRPWM | HRPWM | Actuation_HRPWM | HRPWMConfig |
| UART | COM_UART | Communication_and_Storage | CommunicationConfig |
| SPI | COM_SPI0 | Communication_and_Storage | CommunicationConfig |
| CAN | CAN | Communication_and_Storage | CommunicationConfig |
| Timer Capture | TIMER捕获 | Sensing_Timer | TimerCaptureConfig |
| GPIO | GPIO (IO_OUT/IO_IN) | GPIO_Output / GPIO_Input | GPIOConfig |
| System | NRST, BOOT, EMU, OSC | System | SystemConfig |
{
"Chip_Model": "TAE32G5800",
"Subsystems": {
"Actuation_HRPWM": [ { "Pin_Function": "...", "Frequency_Hz": 10000, ... } ],
"Sensing_ADC": [ { "Pin_Function": "...", "DMA_Enabled": true, ... } ],
"Communication_and_Storage": [ { "Protocol": "UART", "Instance": "UART2", "Pins": [...], ... } ],
"Sensing_Timer": [ ... ],
"GPIO_Output": [ { "Direction": "OUT", ... } ],
"GPIO_Input": [ { "Direction": "IN", ... } ],
"System": [ { "Category": "NRST", ... } ]
}
}
| User Intent | Rule to Load | Description |
|---|---|---|
| Install, setup, dependencies | rules/flow-install.md | Python environment and pip setup |
| Parse Excel, run parser, convert | rules/flow-parse.md | Step-by-step parsing workflow |
| Output format, schema, fields | rules/ref-schema.md | Complete JSON output schema reference |
| Errors, failures, missing data | rules/flow-troubleshoot.md | Diagnosis and fixes for parsing issues |
| File | Impact | Description |
|---|---|---|
rules/flow-install.md | HIGH | Python setup, dependency installation, global tool registration, test execution |
rules/flow-parse.md | HIGH | Pipeline overview, input requirements, CLI options, data processing details |
rules/ref-schema.md | MEDIUM | Pydantic model hierarchy, field descriptions, serialization notes |
rules/flow-troubleshoot.md | HIGH | Decision tree diagnosis, common error messages, data quality checks |
Section index: See rules/_sections.md for loading order and strategy.
For platforms that prefer a single file with all rules, see AGENTS.md.