Embedded Systems Design

8 weeks · 0 milestones

Design an embedded system for a defined application, documenting the hardware-software interface at the level a firmware developer would need to implement it. The design must include: a hardware schematic showing the microcontroller, relevant peripherals (sensors, actuators, communication interfaces), and power supply with all connections labelled, a pin assignment table mapping hardware signals to microcontroller GPIO pins with electrical characteristics (voltage levels, current drive, pull-up/pull-down requirements), a peripheral interface specification for at least 2 hardware interfaces (I2C, SPI, UART, or ADC) with timing diagrams and documented protocol, a firmware architecture document describing the top-level software structure, interrupt strategy, and memory layout, and a test plan with at least 5 hardware verification tests. Preferred proof: a design for a real embedded hardware project with documented hardware bring-up evidence. Accessible alternative: a complete design in Wokwi (browser-based Arduino/ESP32 simulator, free) with simulation evidence that the hardware interface behaves as specified — Wokwi supports real sensor simulation for common I2C and SPI devices. Proof artifacts: the schematic and pin assignment (design artifact) and the interface timing analysis and test plan (analysis artifact). Verification: an embedded systems or electronics engineer reviews the interface specification — 'this I2C pull-up value seems wrong for this bus capacitance; what does that do to your rise time?' — requiring you to reason from your own interface specification.

Sign in to start this outcome and track your progress publicly.