Firmware foundations
Drivers, hardware integration, and mixed-signal bring-up
Low-level drivers and board integration across timing, sensing, communication, power conversion, PCB review, and EMI/EMC debugging.
System path
Where the work lives
- 01MCU peripheral
- 02Driver contract
- 03Board interface
- 04Power & sensing
- 05System state
- 06Instrument evidence
Personal scope
What I owned
- Developed and debugged PWM, ADC, UART, I2C, PMBus, and SPI drivers on 32-bit microcontrollers.
- Integrated sensing modules, LED drivers, power-conversion functions, console interfaces, and battery-powered subsystems.
- Reviewed schematics and PCB layouts for manufacturability, signal integrity, grounding, filtering, and integration risk.
- Used oscilloscopes, logic analyzers, and spectrum analysis to isolate cross-domain faults during bring-up.
Engineering approach
How I reasoned about it
- 1
Define initialization, ownership, timing, error, and recovery behavior before treating a peripheral as integrated.
- 2
Move from rail and clock checks to interface timing and then to application state, preserving evidence at each layer.
- 3
For EMI issues, form source-path-victim hypotheses and choose measurements that can distinguish between them.
Validation
How the signal was checked
- Register and timing checks during driver bring-up
- Logic-analyzer and oscilloscope review of interface behavior
- Cross-domain issue investigation across firmware, power, sensing, motor, and RF
Working vocabulary
Technologies and domains
CPWM/ePWMADCUARTI2CPMBusSPIKiCadEAGLEOscilloscopeLogic analyzer