Establish a Writable Baseline
- Create a fork/clone of the existing flight controller template project.
- Document and annotate the preserved sections of the architecture including the STM32F405, MPU-6000 IMU, MAX7456/AT7456E OSD, power rails (+5V, +3V3, +V_USB, and GND), and signal interface portals (USB, UART, video, etc.).
Capture and Define Interface-Level Requirements
- Specify requirements for the USB-C interface including connector type, expected signal routing for high-speed data lanes, CC pins, and power delivery parameters.
- Define the UART telemetry header requirements by identifying which UART (e.g., UART3 or UART6) will be used, voltage compatibility, and connector pin assignments.
- Determine SWD debug header mapping for the STM32F405, noting necessary signal pins (SWDIO, SWCLK, NRST) and any interfacing constraints.
Map Integration Boundaries and Resource Allocation
- Review the current preserved nets and connector headers to identify any conflicts or resource overlaps with the new interfaces.
- Assign and document which existing MCU peripherals and nets will service the new interfaces without affecting the established functionality for the IMU and OSD.
- Specify constraints on reusing or modifying existing nets and power rails, ensuring continued operation of the original flight controller functions.
Document Implementation-Ready Change Brief
- Convert the above requirements into a detailed change brief for the forked project, including step-by-step instructions for schematic edits and layout updates.
- Define acceptance criteria and verification checkpoints, such as confirmation that the new headers maintain signal integrity and that existing subsystems retain their original functionality.
- Prepare a review checklist to validate that the modifications align with the documented preservation constraints before committing further development steps.