docs: Update information

Author: d3vv3

README.md

@@ -1,11 +1,13 @@
-# Open Motorcycle Intercom (OMI)
+# OpenHelmet
+
+<p align="center">
+    <b>Open Source Mesh and Bluetooth Motorcycle Intercom</b>
+</p>
 
 OMI is an **open‑source, motorcycle intercom system**
 designed to outperform current proprietary solutions
 in **latency, scalability, transparency, and hackability**.
 
-[TOC]
-
 ## Key goals
 - Open protocol and open firmware
 - Real‑time full‑duplex voice
@@ -24,8 +26,9 @@ Interoperability is achieved **only through standard Bluetooth audio profiles**.
 ### Prerequisites
 
 - [ESP-IDF v5.5+](https://docs.espressif.com/projects/esp-idf/en/v5.5/esp32s3/get-started/)
-- ESP32-S3-DevKitC-1-N8R8 (must have PSRAM)
-- USB-C cable
+- [KiCad](https://www.kicad.org/)
+- ESP32-S3-DevKitC-1-N8R8
+- x4 USB-C cables
 - [Audio Hardware Wiring Guide](docs/wiring.md)
 
 ### Build
@@ -35,15 +38,14 @@ Interoperability is achieved **only through standard Bluetooth audio profiles**.
 source ~/esp/esp-idf/export.sh
 
 # Build firmware
-cd omi
 idf.py build
 ```
 
 ### Flash
 
 ```bash
 # Find your serial port
-ls /dev/ttyACM* /dev/ttyUSB* 2>/dev/null
+ls /dev/ttyACM* /dev/ttyUSB*
 
 # Flash firmware (replace PORT with your device)
 idf.py -p /dev/ttyACM0 flash
@@ -81,10 +83,8 @@ I (xxx) audio: Audio task heartbeat: loops=0, encoded=0, decoded=0
 
 | Issue | Solution |
 |-------|----------|
-| Permission denied on serial port | `sudo usermod -a -G dialout $USER` then log out/in |
 | Device not found | Use a data cable (not charge-only), try different USB port |
 | Garbage characters in monitor | Wrong baud rate, use 115200 |
-| PSRAM not detected | Ensure you have the N8R8 variant board |
 
 ---
 
@@ -93,53 +93,43 @@ I (xxx) audio: Audio task heartbeat: loops=0, encoded=0, decoded=0
 - Cardo/Sena mesh protocols are proprietary and closed
 - True mesh interoperability with them is impossible today
 - Voice communication requires **deterministic latency**, not best‑effort networking
-- 2.4 GHz spectrum is congested; protocol efficiency matters more than raw bandwidth
 
-As a result, OMI is designed around **custom real‑time audio transport**,
-not existing consumer mesh standards.
+As a result, OpenHelmet is designed around **custom real‑time audio transport**.
 
 ---
 
-## High‑Level Architecture
+## High Level Architecture and Roadmap
 
 ### Phase 1 (Single‑MCU)
-- **ESP32‑S3**
-- TDMA mesh protocol over ESP-NOW (2.4 GHz)
-- Opus low‑bitrate voice
-- Bluetooth Classic gateway
-
-### Phase 2 (Dual‑MCU, Production‑Grade)
-- **Nordic nRF54**: ESB radio with custom PHY control
-- **ESP32‑S3**: Bluetooth Classic + audio mixing
-- UART/SPI audio & control bridge between MCUs
-
-Phase 1 uses ESP-NOW as the transport layer for rapid prototyping.
-"Custom mesh" refers to the TDMA scheduling and routing protocol built on top.
-True low-level PHY control comes with nRF54's Enhanced ShockBurst in Phase 2.
-
----
+- [x] **ESP32‑S3**
+- [x] TDMA mesh protocol over [ESP-NOW](https://www.espressif.com/en/solutions/low-power-solutions/esp-now) (2.4 GHz)
+- [x] Opus low‑bitrate voice
+- [x] Analog microphone via headphone jack
+- [x] Speaker output via headphone jack
+- [x] VOX for voice activation
 
-## Audio Codec Choice: Opus (Low Bitrate)
+> Phase 1 uses ESP-NOW as the transport layer for rapid prototyping.  
+> The firmware will always remain compatible with ESP-NOW when the nRF52 from Phase 2 is not found at startup.
 
-### Why Opus
-Opus is mandatory for this project.
-No alternative matches its efficiency for real‑time voice.
+### Phase 2 (Dual‑MCU, Production‑Grade)
+- [x] **Nordic nRF52**: [ESB](https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/protocols/esb/index.html) radio with custom PHY control
+- [x] SPI audio & control bridge between MCUs
+- [x] Noise supression, echo cancellation
 
-| Codec | Typical Bitrate | Quality | Packet Loss Resilience |
-|------|---------------|---------|------------------------|
-| CVSD | ~64 kbps | Poor | Very poor |
-| SBC | 48–64 kbps | Fair | Poor |
-| **Opus** | **8–16 kbps** | **Good** | **Excellent** |
+> The firmware will always remain compatible with ESP-NOW when the nRF52 from Phase 2 is not found at startup.  
+> ESP-NOW is not interoperable with nRF52' ESB.
 
-### Target Configuration
-- Mode: VoIP
-- Sample rate: 16 kHz
-- Channels: Mono
-- Bitrate: 8–16 kbps
-- Frame size: 20 ms
-- FEC: Enabled
+### Phase 3 (Triple-MCU, Consumer-Ready)
+- [ ] **FSC-BT1026D** (Qualcom QCC3034) BT5.1 audio SoC
+- [ ] Phone interop via HFP profile
+- [ ] Audio mixing for legacy intercom bridging
 
-This balances clarity, wind tolerance, latency, and bandwidth.
+### Phase 4 (Custom PCB)
+- [ ] Custom PCB design with integrated audio codec and power management
+- [ ] Battery power with charging circuit
+- [ ] Enclosure design
+- [ ] Open‑source manufacturing files
+- [ ] Testing on real motorcycle rides
 
 ---
 
@@ -186,249 +176,3 @@ Used for:
 - Joining/leaving the group
 - Topology updates
 - Slot renegotiation
-
----
-
-## 7. Nordic ESB (Enhanced ShockBurst)
-
-### What It Is
-Nordic ESB is a **lightweight proprietary 2.4 GHz packet radio protocol**
-with minimal overhead and very low latency.
-
-### Why It Matters
-- Sub‑millisecond packet latency
-- Small stack footprint
-- Predictable timing
-- Excellent power efficiency
-
-### Tradeoffs
-- Nordic‑only
-- Requires implementing:
-  - Addressing
-  - Routing
-  - Security
-
-For OMI, these are acceptable and desirable tradeoffs.
-
----
-
-## Hardware Choices Explained
-
-### ESP32‑S3 (Phase 1 Backbone)
-
-**Why it is used initially:**
-- Bluetooth Classic (HFP/A2DP) support
-- Sufficient DSP for Opus
-- Large community and low cost
-- Easy prototyping
-
-**Limitations:**
-- Higher power consumption
-- Bluetooth stack complexity
-- Less deterministic radio control
-
-**Typical Power Use:**
-- Bluetooth audio active: ~60–90 mA
-- Average system: ~120–150 mW
-
-**Battery Life Estimate:**
-- 1000 mAh @ 3.7 V ≈ 3.7 Wh
-- ~24 hours mixed use achievable
-
----
-
-### Nordic nRF52 (Reference / Legacy)
-
-- Excellent low‑power radio
-- Mature SDK
-- Limited RAM for Opus + mesh
-- Bluetooth Classic mostly unavailable
-
-Good for experimentation, not ideal for full system.
-
----
-
-### Nordic nRF54 (Target Mesh MCU)
-
-**Why nRF54:**
-- Much more RAM and CPU
-- Designed for real‑time wireless
-- Extremely low power consumption
-- Ideal for ESB‑based mesh
-
-**Why not yet:**
-- New platform
-- Higher cost
-- Smaller ecosystem (for now)
-
----
-
-## Dual‑MCU Architecture (Final Target)
-
-### Responsibilities Split
-
-**nRF54**
-- ESB mesh
-- TDMA scheduling
-- Routing
-- Ultra‑low power operation
-
-**ESP32‑S3**
-- Bluetooth Classic interop
-- Audio mixing
-- User interface
-
-This keeps Bluetooth complexity isolated and preserves battery life.
-
----
-
-## Interoperability Strategy
-
-OMI **does not join proprietary meshes**.
-
-Instead:
-- Acts as Bluetooth headset or phone
-- Uses HFP profile
-- Bridges one legacy intercom into the open mesh
-
-This is the only realistic interoperability model.
-
----
-
-## Power & Battery Targets
-
-### Design Targets
-- Active riding: 8–16 hours
-- Standby: multiple days
-
-### Battery
-- Li‑Po 1000–1500 mAh
-- USB‑C charging
-
-### Average Power Budget
-- Target: <150 mW
-- Mesh duty cycling
-- VOX‑based audio gating
-
----
-
-## Scalability Model
-
-- 2–4 riders: full mesh
-- 5–8 riders: TDMA with relays
-- 8–10 riders: diminishing returns
-
-Linear motorcycle formations are explicitly exploited.
-
----
-
-## Hardware BOM (Development)
-
-### Recommended Dev Board
-
-**ESP32-S3-DevKitC-1-N8R8**
-
-| Spec | Value |
-|------|-------|
-| MCU | ESP32-S3 (dual-core Xtensa LX7 @ 240 MHz) |
-| Flash | 8 MB |
-| PSRAM | 8 MB (required for Opus + mesh buffers) |
-| Bluetooth | Classic + BLE 5.0 |
-| WiFi | 802.11 b/g/n (ESP-NOW capable) |
-
-**Important:** Get the N8R8 variant (with PSRAM). Boards without PSRAM will not have enough RAM.
-
-### Audio Components (Phase 1)
-
-| Component | Part Number | Purpose | Qty |
-|-----------|-------------|---------|-----|
-| I2S Microphone | INMP441 | Audio capture | 1 |
-| I2S Amplifier | MAX98357A | Speaker output | 1 |
-| Speaker | 4 ohm / 3W | Audio playback | 1 |
-
-### Minimum Development Kit
-
-| Item | Est. Cost |
-|------|-----------|
-| ESP32-S3-DevKitC-1-N8R8 | $12 |
-| INMP441 breakout | $4 |
-| MAX98357A breakout | $4 |
-| Small speaker | $2 |
-| Breadboard + jumpers | $5 |
-| **Total** | **~$27** |
-
-### Multi-Node Testing (Phase 2+)
-
-For mesh development, obtain **2–3 identical setups**.
-
-### Boards to Avoid
-
-| Board | Reason |
-|-------|--------|
-| ESP32-S3 without PSRAM | Insufficient RAM |
-| ESP32 (original) | Less RAM, no native USB debug |
-| ESP32-C3 | Single core, no Bluetooth Classic |
-| ESP32-S2 | No Bluetooth |
-
-### Future Hardware (Phase 4+)
-
-| Component | Purpose |
-|-----------|---------|
-| nRF54 DK | ESB mesh radio MCU |
-| Custom PCB | Production prototype |
-| Li-Po 1000–1500 mAh | Battery |
-| TP4056 or BQ24072 | USB-C charging IC |
-
----
-
-## Project Roadmap
-
-### Phase 0 – Research & Validation
-- Opus benchmarks on ESP32‑S3
-- Latency measurements
-- Power profiling
-
-### Phase 1 – MVP (Single MCU)
-- ESP32‑S3 firmware
-- Opus voice
-- Simple TDMA mesh
-- Push‑to‑talk
-
-### Phase 2 – Mesh Hardening
-- Dynamic slot allocation
-- Packet loss recovery
-- Group management
-
-### Phase 3 – Bluetooth Gateway
-- HFP implementation
-- Audio mixing
-- Legacy intercom bridge
-
-### Phase 4 – Dual‑MCU Prototype
-- nRF54 mesh firmware
-- ESP32 bridge firmware
-- SPI/UART protocol
-
-### Phase 5 – Hardware Refinement
-- Custom PCB
-- Power optimization
-- RF tuning
-
----
-
-## Guiding Principles
-
-- Determinism over throughput
-- Simplicity over standards
-- Open over proprietary
-- Physics always wins
-
----
-
-## Status
-
-This README defines the **technical north star** of the project.
-Implementation details will evolve,
-but the architectural decisions documented here
-are intentional and grounded in real‑world constraints.
-