Name: Electrical Review
Author: pjcau

Skills suchen.../

Skill-Inhalt

Covers the gap between DFM/DRC (manufacturing checks) and actual electrical functionality. Verifies that the board will boot, power up correctly, and operate reliably.

Steps

1. Run automated electrical checks

cd /Users/pierrejonnycau/Documents/WORKS/esp32-emu-turbo

# 1a. Strapping pin verification (12 tests)
python3 scripts/verify_strapping_pins.py

# 1b. Decoupling capacitor adequacy (25 tests)
python3 scripts/verify_decoupling_adequacy.py

# 1c. Power sequencing verification (26 tests)
python3 scripts/verify_power_sequence.py

# 1d. SPICE power supply simulation (requires ngspice)
python3 scripts/spice_power_check.py

Script	Tests	What it catches
`verify_strapping_pins.py`	12	Wrong boot state, GPIO45 VDD_SPI conflict, EN RC timing
`verify_decoupling_adequacy.py`	25

# 1e. Component connectivity + signal chain completeness
python3 scripts/verify_component_connectivity.py
python3 scripts/verify_signal_chain_complete.py

#	Question	What to check
A1	Are all power rails isolated from each other (no shorts)?	Run `python3 scripts/verify_power_paths.py`, check net isolation
A2	Is the power switch between battery and IP5306?	Check SW_PWR pads in PCB cache, verify BAT+ net routing
A3	Are USB CC1/CC2 pull-downs correct (5.1k to GND)?	Check R1, R2 values (5.1k) and nets (USB_CC1/CC2 to GND)
A4	Is reverse polarity protection adequate?	Check BAT54C diode D1, JST connector polarity

#	Question	What to check
B1	Does IP5306 boost start cleanly from 3.7V battery?	Check C17 (VIN), L1 (inductor), C19/C27 (VOUT) values
B2	Is AMS1117 dropout voltage met? (+5V - 3.3V = 1.7V > 1.3V dropout)	AMS1117 datasheet: dropout 1.3V max, margin = 0.4V
B3	Does EN pin RC delay allow supply to stabilize?	R3=10k, C3=100nF, tau=1ms, 3*tau=3ms < 5ms sample window
B4	Is IP5306 KEY pin properly configured?	R16=100k pull-down, check KEY net routing
B5	Can charge-and-play work? (USB + battery simultaneously)	IP5306 supports charge-and-play natively

#	Question	What to check
C1	Is GPIO0 HIGH at boot? (normal boot vs download mode)	BTN_SELECT pull-up R9=10k to +3V3, button not pressed = HIGH
C2	Is GPIO45 LOW at boot? (VDD_SPI=3.3V for PSRAM)	R14 DNP + i=10 skip in routing.py, no external pull-up
C3	Is GPIO46 LOW at boot? (ROM log output)	LCD_WR has internal pull-down, no external pull-up
C4	Does GPIO3 state matter?	Any state OK (USB JTAG select), pull-up is acceptable
C5	Is PSRAM accessible at boot? (Octal SPI, needs VDD_SPI=3.3V)	Depends on C2 (GPIO45=LOW), verified by strapping check
C6	Is flash accessible? (16MB SPI flash on module)	Module has internal flash connection, no external routing needed

#	Question	What to check
D1	Can ESP32 source enough current for all peripherals?	Total: ~350mA max (WiFi burst), AMS1117 rated 1A
D2	Is display bus functional? (8-bit 8080 parallel)	Check LCD_D0-D7, CS, RST, DC, WR traces; LCD_RD tied HIGH; LCD_BL via resistor
D3	Is SD card SPI functional?	Check SD_MOSI, SD_MISO, SD_CLK, SD_CS routing to TF-01A
D4	Is I2S audio path clean?	Check I2S_BCLK, I2S_LRCK, I2S_DOUT to PAM8403; DC-blocking cap C22
D5	Are all buttons readable?	12 buttons + menu combo via BAT54C D1
D6	Is USB data path functional?	D+/D- through USBLC6-2SC6 (U4), 22ohm series (R22/R23), to ESP32
D7	Is speaker output adequate?	PAM8403 3W per channel, SPK+/SPK- to 28mm speaker
D8	Are LEDs functional?	LED1/LED2 through R17/R18 (1k), connected to IP5306 LED outputs
D9	Is thermal dissipation adequate?	AMS1117: P=(5-3.3)*0.35=0.6W, SOT-223 can handle ~1.5W with thermal pad

#	Question	What to check
E1	What happens if USB is plugged in while battery is low?	IP5306 handles charge-and-play, VBUS powers via VIN
E2	What happens if battery is removed while USB powers the board?	IP5306 VOUT continues from VBUS, check C19 bulk cap for transient
E3	Can EMI from boost converter affect ESP32?	Check L1-to-ESP32 distance, GND plane shielding on In1.Cu
E4	Is antenna keepout zone clear?	Run verify_antenna_keepout.py, check no copper within 5mm
E5	Can button bounce cause false triggers?	100nF debounce caps + firmware debounce (typically 20ms)
E6	Is ESD protection adequate on exposed connectors?	USB: USBLC6-2SC6 TVS, SD card: internal to TF-01A module

## Electrical Review Report

**Board**: ESP32 Emu Turbo v3.x
**Date**: [date]

### Automated Checks
| Script | Result | Tests |
|--------|--------|-------|
| verify_strapping_pins.py | PASS/FAIL | X/Y |
| verify_decoupling_adequacy.py | PASS/FAIL | X/Y |
| verify_power_sequence.py | PASS/FAIL | X/Y |
| spice_power_check.py | PASS/FAIL | X/Y |

### Manual Review
| Section | OK | CONCERN | RISK |
|---------|----|---------|----- |
| A. Pre-Power (4) | X | X | X |
| B. Power-Up (5) | X | X | X |
| C. ESP32 Boot (6) | X | X | X |
| D. Runtime (9) | X | X | X |
| E. Edge Cases (6) | X | X | X |

### Critical Issues (RISK)
[List any RISK verdicts with evidence]

### Concerns (CONCERN)
[List any CONCERN verdicts with evidence]

### Overall Verdict: PASS / CONDITIONAL PASS / FAIL

File	Purpose
`scripts/verify_strapping_pins.py`	ESP32-S3 boot pin configuration (12 tests)
`scripts/verify_decoupling_adequacy.py`	IC decoupling per datasheet (25 tests)
`scripts/verify_power_sequence.py`	Power chain and sequencing (26 tests)
`scripts/spice_power_check.py`	SPICE simulation of power rails
`scripts/generate_schematics/config.py`	GPIO mapping (source of truth)
`scripts/generate_pcb/routing.py`	PULL_UP_REFS, NET_ID, pad nets
`software/main/board_config.h`	Firmware pin definitions
`hardware/datasheet_specs.py`	Component pin-to-net specs

Electrical Review | Skills Pool

Electrical Review

Electrical Review

Steps

1. Run automated electrical checks

2. Manual 30-question electrical review

A. Pre-Power (4 questions)

B. Power-Up Sequence (5 questions)

C. ESP32 Boot (6 questions)

D. Runtime (9 questions)

E. Edge Cases (6 questions)

3. Generate verdict report

Key Files

Automation Audit Ops

Github Qa Labels

Jupyter Notebook

Tidb Integrationtest Recorder

Quality Nonconformance

Hugging Face Trackio