Source baseline
Find the public firmware source on GitHub. Check the version file for your board in the source you download, and use the official flashing tool to see available firmware releases. A source version does not by itself mean that a matching binary has been released. Match hardware instructions to your kit revision.
Changes reflected in this handbook
- TARS is included as a separate board with a landscape ST7789V2 terminal display.
- TARS motion, calibration, touch sleep and personality settings are documented separately.
- Arm teach-and-replay behavior is described as a current-power-session recording.
- Version numbers come from per-board version.txt files.
- Packaging selects the board and builds both China and international configurations.
Developer version commands
python tools/version.py list
python tools/version.py get tars
python tools/package_luwu_firmware.py --board tars --dry-run
The dry run prints the plan; it does not validate a compiled image. Remove --dry-run only when you intend to build the packages in an initialized ESP-IDF environment.
Editorial sources
Chinese RIG product, assembly, quick-start and software articles supplied the user workflows. Board classes, Kconfig, display configuration and packaging scripts supplied implementation details. Where old text conflicts with the current implementation, this handbook uses the reviewed code behavior and avoids assuming identical controls across models.
TARS public build and packaging
The public source now includes main/boards/tars/ and RIG-Tars in the board menu. Follow the complete TARS workshop with ESP-IDF 5.5.3. The packaging dry run above only prints a plan. Full packaging also requires a separate Test_Firmware/ or test_firmware/ project; use the ordinary idf.py build / flash workflow when building only the robot firmware. See TARS package paths and prerequisites.