forked from odriverobotics/ODrive
-
Notifications
You must be signed in to change notification settings - Fork 0
Build
Bogdan Seczkowski edited this page Dec 14, 2025
·
1 revision
This page covers the common build steps for the firmware in this repository.
Prerequisites (Linux example)
- Python 3.8+
pipgcc-arm-none-eabi-
openocd(for ST-Link flash targets) -
stlink-tools(optional) -
tup(the Makefile usestupduring the build) make
Install common packages on Debian/Ubuntu:
sudo apt update
sudo apt install -y python3 python3-pip make gcc-arm-none-eabi openocd stlink-tools tupBuild steps
cd Firmware
make
# or parallel: make -j$(nproc)After a successful build, firmware artifacts live in Firmware/build/ (for example ODriveFirmware.hex and ODriveFirmware.elf).
Flash using ST-Link / OpenOCD
cd Firmware
make flash # uses openocd & stlink (flash-stlink2 target)Other targets in the Firmware/Makefile include: clean, flash-bmp, dfu, erase, unlock, and libfibre-* build helpers.
Notes
- The Makefile will call
tup— ensuretupis installed and configured. - Building the Python tools (odrivetool) is done in the
toolsfolder. Install withpip install -e toolsfor local development.