How marzac/zekit works
ZeKit is an embedded firmware project for a DIY paraphonic synthesizer. Its principal workflow is user or MIDI input being handled by firmware and producing synthesized audio; the source tree also identifies sequencing, waveform, UI, persistence, and device setup responsibilities. The README confirms the firmware is built and flashed to the board, but the sampled source does not show runtime call relationships, so those links are marked unverified. The schematics provide the hardware context.
Main entry points: main.c Firmware Entry · audio.c Audio Engine · setup.c Device Setup · ui.c User Interface
Components 16
Input and Control
- User Interface
Firmware/ui.c - MIDI Handling
Firmware/midi.c - Music Sequencer
Firmware/mseq.c
Sound Generation
- Audio Engine
Firmware/audio.c - Waveform Data
Firmware/waves.c
Device Platform
- Firmware Entry
Firmware/main.c - Device Setup
Firmware/setup.c - Interrupt Handling
Firmware/interrupts.c - Fault Traps
Firmware/traps.c - Board Configuration
Firmware/config.h - Pin Mapping
Firmware/pins.h - State Storage
Firmware/store.c - Firmware Image
Firmware
Hardware
- Synthesizer Board
Schematics
Other components
- Musician
- MIDI Source
Connections 17
- Musician → User Interface: controls
- MIDI Source → MIDI Handling: sends MIDI
- Firmware Entry → Device Setup: initializes
- Firmware Entry → User Interface: runs
- Firmware Entry → MIDI Handling: runs
- Firmware Entry → Music Sequencer: runs
- Firmware Entry → Audio Engine: runs
- Firmware Entry → Interrupt Handling: uses
- Firmware Entry → Fault Traps: uses
- Device Setup → Board Configuration: configures
- Device Setup → Pin Mapping: configures
- User Interface → State Storage: accesses state
- MIDI Handling → Music Sequencer: dispatches events
- Music Sequencer → Audio Engine: provides events
- Audio Engine → Waveform Data: uses
- Audio Engine → Synthesizer Board: outputs audio
- Firmware Image → Synthesizer Board: flashed to
README.md