GDEY029T71H vs GDEY029T94 Was Not a Cosmetic Part-Number Detail
The display firmware could be perfectly written for the wrong panel if the exact part number was not reconciled with the schematic.
TOPIC
PCB Bring-Up & Hardware
Lessons, explainers, experiments, and implementation notes.
ES8311 and ES7210 Split the Audio Problem in Two
Speaker and microphone failures were easy to discuss as one audio problem even though playback and capture used different codecs and different analog paths.
A Tinny Speaker Is Not Automatically an ES8311 Problem
Field feedback described the EVT speaker as very tinny even though the digital voice path and codec communication were functioning.
USB-C Charging Is Not a Factory Debug Strategy
A product can have a USB-C connector and still lack a reliable programming/recovery path for failed units.
DFM Means Alignment Cannot Depend on Human Guesswork
A prototype can be assembled carefully by an engineer even when its geometry is too ambiguous for repeatable production.
The Rotary Encoder Datasheet and the Desired Feel Disagreed
The proposed encoder had push and six pulses per revolution, but its datasheet listed zero rotational detents while the product required clear tactile detents.
EVT Approval Is Not Mass-Production Approval
Moving quickly toward EVT created pressure to interpret every interim approval as a final product freeze.
An E-Paper BUSY Timeout Can Be Power or FPC, Not Firmware
A BUSY timeout is easy to interpret as a display-driver bug, but the panel can remain busy or silent when its power rail or flex connection is wrong.
A Pin Map Is an Interface Contract, Not a Convenience Header
Audio debugging depended on exact MCLK, BCLK, LRCK, data and control wiring, yet pin values could easily be copied from stale board revisions.
The Manufacturer/Firmware Boundary Needs a Written Interface
Hardware and firmware teams could each make locally reasonable decisions that violate assumptions on the other side unless ownership and interfaces were explicit.
The Schematic, BOM and Firmware Must Describe the Same Product
Board bring-up became risky whenever the schematic, BOM, datasheet package and firmware assumptions described different parts or behaviors.
An AXP2101 Datasheet Is Not a LOUP Power Tree
Receiving the PMIC datasheet did not answer which regulator powered each subsystem, what came up before firmware, or how the product behaved on battery and USB insertion.
A 100 Percent End-of-Line Test Needs Traceability, Not Just a Green LED
A factory test that says PASS without linking the result to a specific unit, programmed identity and relevant component history is weak forensic evidence.
Define the Questions Before Calling EVT a Success
Seeing a prototype power on is a major relief, but engineering validation requires knowing which questions the board has actually answered. One LED cannot validate power, audio, radio behavior, and long-duration operation at the same time.
FLASH_PORT and Test Pads Are Insurance for the Unit That Does Not Boot
Factory and service workflows need a path that still works when firmware, provisioning or normal UI cannot start.
A WS2812 Powered from VBAT Makes Logic Margin a Hardware Question
The single RGB status LED looked like a simple GPIO peripheral, but the schematic powered the WS2812B-2020 from a switched VBAT-derived RGB_VDD while its data came from the ESP32 domain.
GPIO17 Was Not Enough to Explain the Speaker PA Control
Historical board notes associated amplifier enable with GPIO17, while later verified board-path evidence showed the physical speaker PA controlled through TCA9555 EXIO08 in the working implementation.
The Antenna Does Not End at the Edge of the Board
A board antenna gives clues about expected behavior, but in a real product the surrounding objects become part of the system. The enclosure, cables, metal parts, and device placement can all change the result. An open-board test is not a guarantee for the finished enclosure.
Some Boot Bugs Exist Before app_main Ever Runs
Peripheral connections on ESP32-S3 strapping pins can influence reset before application diagnostics have a chance to run.
Runtime Probes Beat Human-Friendly Channel Names
The Minewing ES7210 wrapper labeled four int16 positions as four physical channels, but the host transport packing did not match those names.
NC on the Schematic Does Not Mean the Regulator Is Disabled
Unused AXP2101 regulator pins could appear electrically unconnected while still being enabled internally by default or firmware.
The EVT Slide Switch Should Not Define the Production Power Model
The prototype’s physical power behavior risked becoming a permanent architecture even though the production product needed deliberate momentary power/wake semantics.
STD 2x32 Beat My “More Obvious” TDM 4x16 Experiment
Seeing four 16-bit-looking positions in memory made true four-slot TDM seem like the natural host configuration.
I2C Detection Proves Presence, Not Functional Correctness
Seeing ES8311, ES7210 and AXP2101 on the I2C bus was necessary but insufficient evidence that the audio and power architecture worked correctly.
MIC3 Was an Electrical Speaker Reference, Not Just Another Microphone
AEC debugging initially suffered because the channel expected to carry a far-end reference appeared almost dead.
One Microphone or Two Is a System Decision
The microphone count could not be chosen only by firmware or only by mechanical design because it changes acoustics, channels, BOM, placement, assembly and test.
ALDO2 and ALDO3 Became Named Product Rails
Display and audio bring-up failed more predictably once regulator names were tied to actual product loads instead of generic PMIC outputs.