16.7K ·GitHub
What is this?
The official open-source firmware that runs on the Flipper Zero — a pocket-sized multi-tool device (the dolphin) that talks to radios, cards and readers around you.
The official open-source firmware that runs on the Flipper Zero — a pocket-sized multi-tool device (the dolphin) that talks to radios, cards and readers around you.Does this run on my computer, or on the device itself?On the device: this repo is the source code of the firmware that lives on the Flipper Zero itself. Your computer is only used to build the code and flash it onto the dolphin.
On the device: this repo is the source code of the firmware that lives on the Flipper Zero itself. Your computer is only used to build the code and flash it onto the dolphin.How do I get the firmware onto my Flipper?Clone this repo and build it with the Flipper Build Tool, then flash it either over USB while the Flipper is on, or with an in-circuit debugger.
Clone this repo and build it with the Flipper Build Tool, then flash it either over USB while the Flipper is on, or with an in-circuit debugger.What do I need installed before I can build it?Windows 10+, macOS 12+ or Ubuntu 20.04+ with Git and basic build tools; the Flipper Build System takes care of all other dependencies. An in-circuit debugger (ST-Link, J-Link, CMSIS-DAP probe or the Wi-Fi Dev Board) is optional but highly recommended.
Windows 10+, macOS 12+ or Ubuntu 20.04+ with Git and basic build tools; the Flipper Build System takes care of all other dependencies. An in-circuit debugger (ST-Link, J-Link, CMSIS-DAP probe or the Wi-Fi Dev Board) is optional but highly recommended.Do I need to be an experienced C developer to work with it?An intermediate level of C is recommended for comfortable programming; Flipper applications themselves can be written in C, C++ or armv7m assembly.
An intermediate level of C is recommended for comfortable programming; Flipper applications themselves can be written in C, C++ or armv7m assembly.Can I modify the firmware and flash my own builds?Yes — the code is GPL-3.0, so custom builds are fine as long as they keep the same license. Changes meant for the mainline must be compatible with the project license and pass CI.
Yes — the code is GPL-3.0, so custom builds are fine as long as they keep the same license. Changes meant for the mainline must be compatible with the project license and pass CI.What can the Flipper actually do with this firmware?It drives the device's radios and readers: Sub-GHz radio, RFID, NFC, infrared, one-wire iButton and Bluetooth LE, per the repo's topics. There is also a universal infrared remote database you can contribute your own remotes to.
It drives the device's radios and readers: Sub-GHz radio, RFID, NFC, infrared, one-wire iButton and Bluetooth LE, per the repo's topics. There is also a universal infrared remote database you can contribute your own remotes to.Can I add my own apps without forking the whole firmware?Yes. There is an applications_user folder for your own apps and services, and the maintainers note that many ideas are better implemented as external applications published in the Flipper Application Catalog rather than merged into the firmware.
Yes. There is an applications_user folder for your own apps and services, and the maintainers note that many ideas are better implemented as external applications published in the Flipper Application Catalog rather than merged into the firmware.What is Furi?Furi Core is the OS-level layer of the firmware — the primitives and helpers everything else builds on. In the source tree it sits in its own furi directory, next to lib for shared libraries and targets for platform-specific code.
Furi Core is the OS-level layer of the firmware — the primitives and helpers everything else builds on. In the source tree it sits in its own furi directory, next to lib for shared libraries and targets for platform-specific code.What happens if a bad flash bricks my Flipper?The developer documentation covers hardware combos and un-bricking for recovering the device from the nastiest states — one reason an in-circuit debugger is recommended for low-level work.
The developer documentation covers hardware combos and un-bricking for recovering the device from the nastiest states — one reason an in-circuit debugger is recommended for low-level work.What are similar projects?ESP32-Bit-Pirate, unleashed-firmware, Marlin, mongoose, ESP32Marauder, PLFM_RADAR, tinygo, Dummy-Robot
ESP32-Bit-Pirate, unleashed-firmware, Marlin, mongoose, ESP32Marauder, PLFM_RADAR, tinygo, Dummy-RobotWhich topics is it in?flipperzero, bluetooth-le, stm32, assembly, microcontroller, firmware, embedded, hardware, c, cpp, developers, gplv3
flipperzero, bluetooth-le, stm32, assembly, microcontroller, firmware, embedded, hardware, c, cpp, developers, gplv3