GitXplorerGitXplorer
f

flipperzero-firmware

public
12486 stars
2679 forks
155 issues

Commits

List of commits on branch dev.
Verified
913a86bbec7c9590692e00c1a7b0a74c36a4360c

kerel typo (#3901)

EEntranceJew committed 4 days ago
Verified
19a3736fe5dab5d01220660b318fed824a2d6e22

[FL-3891] Folder rename fails (#3896)

pportasynthinca3 committed 4 days ago
Verified
b670d5b6e2081bec5abcf3a693db5ce3af5d8ab2

[FL-3885] Put errno into TCB (#3893)

pportasynthinca3 committed 6 days ago
Verified
0428e82b14065e36cdae352b1b59a6ededa3c6f8

Fix USB-UART bridge exit screen stopping the bridge prematurely (#3892)

pportasynthinca3 committed 7 days ago
Verified
5f4f4fcc60f587962b0518b7d58523b4d0bab6de

FeliCa anti-collision fix (#3889)

RRebornedBrain committed 10 days ago
Verified
78c5dd95d867941206e1be2fd3585c9c76132bd7

LFRFID GProxII Fix Writing and Rendering Conflict (#3888)

zzinongli committed 10 days ago

README

The README file for this repository.
A pixel art of a Dophin with text: Flipper Zero Official Repo

Flipper Zero Firmware

Contributing

Our main goal is to build a healthy and sustainable community around Flipper, so we're open to any new ideas and contributions. We also have some rules and taboos here, so please read this page and our Code of Conduct carefully.

I need help

The best place to search for answers is our User Documentation. If you can't find the answer there, check our Discord Server or our Forum. If you want to contribute to the firmware development, or modify it for your own needs, you can also check our Developer Documentation.

I want to report an issue

If you've found an issue and want to report it, please check our Issues page. Make sure the description contains information about the firmware version you're using, your platform, and a clear explanation of the steps to reproduce the issue.

I want to contribute code

Before opening a PR, please confirm that your changes must be contained in the firmware. Many ideas can easily be implemented as external applications and published in the Flipper Application Catalog. If you are unsure, reach out to us on the Discord Server or the Issues page, and we'll help you find the right place for your code.

Also, please read our Contribution Guide and our Coding Style, and make sure your code is compatible with our Project License.

Finally, open a Pull Request and make sure that CI/CD statuses are all green.

Development

Flipper Zero Firmware is written in C, with some bits and pieces written in C++ and armv7m assembly languages. An intermediate level of C knowledge is recommended for comfortable programming. C, C++, and armv7m assembly languages are supported for Flipper applications.

Firmware RoadMap

Firmware RoadMap Miro Board

Requirements

Supported development platforms:

  • Windows 10+ with PowerShell and Git (x86_64)
  • macOS 12+ with Command Line tools (x86_64, arm64)
  • Ubuntu 20.04+ with build-essential and Git (x86_64)

Supported in-circuit debuggers (optional but highly recommended):

Flipper Build System will take care of all the other dependencies.

Cloning source code

Make sure you have enough space and clone the source code:

git clone --recursive https://github.com/flipperdevices/flipperzero-firmware.git

Building

Build firmware using Flipper Build Tool:

./fbt

Flashing firmware using an in-circuit debugger

Connect your in-circuit debugger to your Flipper and flash firmware using Flipper Build Tool:

./fbt flash

Flashing firmware using USB

Make sure your Flipper is on, and your firmware is functioning. Connect your Flipper with a USB cable and flash firmware using Flipper Build Tool:

./fbt flash_usb

Documentation

Project structure

  • applications - Applications and services used in firmware
  • applications_users - Place for your additional applications and services
  • assets - Assets used by applications and services
  • documentation - Documentation generation system configs and input files
  • furi - Furi Core: OS-level primitives and helpers
  • lib - Our and 3rd party libraries, drivers, tools and etc...
  • site_scons - Build system configuration and modules
  • scripts - Supplementary scripts and various python libraries
  • targets - Firmware targets: platform specific code

Also, see ReadMe.md files inside those directories for further details.

Links