Crazyflie

Firmware targets are model-specific

The preserved build guide uses cf2_defconfig for Crazyflie 2.0 and 2.1(+), cf21bl_defconfig for 2.1 Brushless and bolt_defconfig for Bolt. The platform documentation explains that supported device types can select different sensor drivers at runtime, while an unsupported hardware identifier causes the firmware to halt. A shared product name is therefore not enough to choose a binary. [S005] [S006]

The README separately says the 2017.06 release was the last with Crazyflie 1.0 support. Do not infer support for that older aircraft from the selected modern archive. [S001]

A source archive is only part of the development environment

The documented build needs an ARM toolchain and make, with recursive Git submodules for components including CMSIS, FreeRTOS, CMock, Unity and libdw1000. The preserved primary archive does not establish complete matching submodule payloads. The build guide also warns that spaces in the checkout path are unsupported. No compilation or unit tests from upstream were run here. [S005] [S007]

For radio flashing, the guide requires Crazyradio, its drivers and the Crazyflie client. Its Windows route builds under WSL but uses the client installed on Windows. The guide distinguishes discovery-based bootloader flashing from an address-specific route, warning that several aircraft in bootloader mode make discovery ambiguous. This is an upstream configuration requirement, not a flashing procedure verified by this review. [S005]

The selected aircraft has a second MCU for radio and power management. This review covers the main firmware archive and does not claim that every matching firmware component or external positioning setup has been preserved. A complete delivered cost also depends on the radio, host and selected decks, not just the aircraft kit. [S005] [S007] [S009]

Hardware documents and source rights have separate limits

The preserved hardware repository includes the 2.1 datasheet, a revision B schematic PDF and a component-placement PDF. Those help identify the design, but do not establish a complete editable PCB or mechanical manufacturing package in the selected 2.1 directory. Hardware-specific rights remain unresolved. [S009] [S010]

There is also a licensing inconsistency in the firmware snapshot: its README says LGPL-3.0, while LICENSE.txt contains GPL version 3 and the inspected stabilizer.c header explicitly grants GPL version 3. The profile records that conflict rather than assigning one unqualified license to the entire tree. Dependencies need their own notice review. [S001] [S003] [S007] [S008]

No kit assembly, firmware installation, radio test, positioning experiment or flight was performed. The entry supports choosing and preserving a configuration for further work; it does not validate flight performance or a complete reproduction. [S005] [S009] [S010]