How notfastenuf/nfe_silverware works
Project type and purpose
• This is an embedded firmware project (“SilverWare – BoldClash BWHOOP B-03 version”) targeting an STM32F0 microcontroller on a micro-quadcopter flight controller board (Bwhoop/E011/H8mini).
• Purpose: read sensors (IMU), decode RC input, run control loops (PID, filters), drive motors (PWM/DShot), manage features (arming, failsafe, telemetry), and expose configuration and telemetry interfaces (BLE, serial).
File structure
• Top-level directories:
• Libraries – CMSIS core headers, ST StdPeriph drivers for all STM32F0 peripherals (GPIO, SPI, I2C, ADC, TIM, USART, etc.)
• Silverware – application code: main.c, control loops, sensor drivers (drv_adc, drv_spi, imu), RC protocols (rx_*.c), motor drivers (drv_pwm, drv_dshot), feature modules (buzzer, gestures, telemetry)
• Utilities – board support files (pin-mapping and configuration for Nucleo, evaluation boards, stm32f0xx_conf.h, system_stm32f0xx.c)
• gcc – alternate build system (Makefile, linker script, flash script)
• bin – prebuilt firmware images
• docs, INSTALL.md, README.md, Makefile, .travis.yml – documentation and CI/build integration
• Key architectural patterns:
• Hardware Abstraction Layer using CMSIS + StdPeriph drivers
• Modular drivers for each peripheral and protocol
• Layered control: sensor acquisition → state estimation/filters → PID control → actuator output
• Compile-time configuration via config.h and pid.c
Insights from the README
• Multiple build targets: Keil µVision IDE or GCC/Make
• Configurable hardware selection via config.h
• Gesture-based on-flight reconfiguration (PID tuning, binding, accel calibration)
• Multi-protocol RC support (Bayang, SBUS, DSM, CRSF, etc.) and optional analog AUX channels
• Telemetry output via BLE (“SilverVISE” Android app) or serial passthrough (4-way interface)
Detailed coverage
• ConfigModule → compiles into Driver and Control modules
• HAL → consumed by all Drivers
• Build System → codebase → binary
• Avoid over-aggregation; split by function and protocol variation to capture architectural breadth